Mobilizing Enterprise Data - Strategies to succeed in enterprise mobile

Mobilizing Enterprise Data - Strategies to succeed in enterprise mobile

• 1.
  Mobilizing Enterprise Data by Alex Zaltsman,CEO InnoviMobile
• 2.
  Mobile Integration Plan IdentifyThe Information Security Plan Implementation Options Project Action Plan Blank Project Action Plan Adoption Formula Plan for integrating Components and Stakeholders Identify Staffing Requirements Contents 9 2 6 7 8
• 3.
  Mobile Integration Plan AdoptionFormula There are many components of an optimal mobile strategy but the most significant is the design for adoption. Creating a fancy user interface with limited functionality, or deploying an application with too strict security will lead to the app being deemed unusable resulting in wasted time and effort. We express the elements of successful mobile deployment as a simple formula: The first two operands, Usability and Desirability, are inextricably linked. They illustrate the core of the most important factors that employees will consider when using a mobile application. MOBILIZING ENTERPRISE DATA 2 (Usability + Desirability) × Security = Adoption Usability Usability is more of an art than a science. Significant thought needs to go into the design, which does not need to be complex. In fact, less complex is better! The application must be easy and intuitive to wield without the need for an instruction guide. The ides is to make the jobs of employees easier, not harder. Desirability Creating desire means crafting an emotional shift from a less desirable alternative (legacy technology) to a more desirable product. If you cannot envision a positive emotional outcome as a result of using the mobile app then adoption will suffer. The mobile app must make an emotional connection with the employees and make a meaningful difference to them.
• 4.
  Plan For IntegratingComponents And Stakeholders It’s important to identify the components that will interface directly or indirectly with mobile applications. Some examples include: The last operand is Security. Note the use of the mathematical symbol for multiplication; the purpose is to emphasize the significance of security of any enterprise mobile application deployment. IT management needs to be able to sleep at night knowing that data that is accessible on mobile devices is secure. Employees need to feel comfortable that security is the cornerstone of the application they use every day, yet it needs to be transparent. Though it is strongly encouraged that a general education plan and policies around mobile security are implemented, users should not be burdened with any complexities associated with IT management’s security requirements as this will impact the first two operands — usability and desirability. MOBILIZING ENTERPRISE DATA 3 CLIENT/SERVER OR WEB APPLICATIONS PRODUCT EXPERT LIAISON ACCESS TO DATA FROM INTRANET DATABASES ACCESS TO DATA FROM INTERNET APPLICATION SUPPORT THIRD-PARTY VENDOR SERVER TEAM ADMIN PRODUCT USER NETWORK ADMIN DATABASE ADMIN FIREWALL/SECURITY ADMIN DESKTOP SUPPORT CONTACT VENDOR SUPPORT CONTACT Some questions you may need to ask while developing your mobility vision: 1.) Does this app make the employee’s day easier and allow them to focus on more meaningful tasks? 2.) How many less steps will the employee take by using mobile technology? 3.) How will the contemplated mobile technology reduce stress, anxiety, and increase passion and creativity on the employee’s role? 4.) Will the mobile technology position the company (and employees) to be viewed as more technologically advanced than competitors? Some questions you may need to ask while developing your mobility vision: Component Stakeholder
• 5.
  In general, itis best to meet with various users of the existing applications, and those who will likely use the mobile version, along with all technical contacts that will provide technical support. The user, also referred to as the “product expert,” is uniquely positioned to explain how the application is utilized in its current state and can make recommendations on features and functionality required for the application on a mobile device. Product experts can also serve as the interface to others in providing feedback. All other roles are typically of a technical nature and will need to work closely with the users of the applications to ensure the goals of the mobile product are met. Identify Staffing Requirements Based on your project timelines does your company have the internal expertise to deliver a finished product that meets the requirements of the user community? Title Role Sets the vision and goals. Understands mobile ecosystem, defines feature set. Coordinates tasks between developers, designers, and communicates project updates to Product Manager and Product Executive. Staff experiences in user experience/user interface design for mobile. Developers to write the code for the platforms necessary to support your product. MOBILIZING ENTERPRISE DATA 4 A typical mobile project will require: Project Executive Product Manager Project Manager Designer(s) Mobile platform developers Server developers Developers for any back-end systems integration.
• 6.
  Team in placebut stretched too thin, or no time to put team together Execute with in-house team. Augment with external resources in case of time constraints. It is critical to choose a partner, not just an outsourcing firm. Many outsourcing firms provide just the software development portion. While enterprise organizations have various resources, it takes significantly more than software development alone to create a mobile application that is widely adopted, secure and implemented within budget. Situation Outcome Team with mobile experience is in place with guaranteed resources Several, but not all key team members are on staff Entire team is in place but seeks guidance on strategy Consider partnering with a mobile development firm that can fulfill the needs of all roles Consider partnering with a mobile development firm that can fill in the gaps Consider partnering with a mobile development firm that can help with mobile strategy MOBILIZING ENTERPRISE DATA 5 Typical scenarios depicting how enterprises approach mobile applications development:
• 7.
  Preparing your informationsecurity infrastructure prior to or concurrently with mobile applications development initiatives will make your team better prepared for the launch of your mobile product. Some of the components that take care of data security, such as Good Dynamics, need to be integrated into the mobile application during development. Category Threat Solution Data in Motion and Data In Use Data At Rest Mobile Application Management Mobile Application Distribution Unauthorized access to data while being transmitted over local and wireless networks. Attempts to decompile the mobile application and unauthorized access to app data storage containers. Lost or stolen devices with apps that access corporate data. Publishing internal apps to public app stores exposes proprietary applications to the general public. End-to-End encryption of data while in transit from the source servers to the mobile device. We recommend Good Technology’s Dynamics product. Encryption of data stored on the device. We recommend Good Technology’s Dynamics product. Platform that provides ability to remotely remove mobile apps from the device. We recommend AppCentral’s Management Console and AppGuardian (recently acquired by Good Technology). AppCentral’s Mobile Storefront provides an internal app store for internal app distribution. MOBILIZING ENTERPRISE DATA 6 Security in the context of mobile applications generally falls into the following categories: Identify the Information Security Plan The key essentials of mobile application security include connectivity and encryption of data during transmission and on the device. Management and control of applications is necessary to prevent unauthorized access in case of device loss or theft.
• 8.
  It’s very importantto choose the right approach for your project and budget from the beginning. Changing approaches during your mobile project will delay deployment and could significantly increase costs while impacting the user experience. Perspective Tools Outcome Individual platform SDKs Web Based platform Centralized platform Hybrid Native device development tools. HTML5 MEAP Native, HTML5, MEAP Best experience and performance that uses native device features and unique UI capabilities. Support for offline use, push notifications, strong analytics. Capabilities of mobile web sites are limited to the capabilities and UI of mobile web browsers. Offline use (other than caching) is not supported. Requires strong Internet connectivity, either cellular or WiFi. Rudimentary experience, lowest common denominator approach to do “build once, deploy to many” development methodology. Source code usable only with MEAP vendor’s platforms. Significant vendor lock-in. Significantly more complex development and maintenance by having to integrate disparate tools and technologies. Some benefits could be achieved by re-using existing web technology. Four Approaches To Mobile Technology In The Enterprise * MOBILIZING ENTERPRISE DATA 7 Implementation Options Deciding on the right approach for development is highly dependent on the specific application that is being contemplated. There are four general approaches to implementing mobile technology in the enterprise. * MEAP was coined by Gartner in a 2008 Magic Quadrant report and is an acronym for Mobile Enterprise Application Platform. MEAP tools are typically purchased and hosted on-premise or used as Software as a Service web site. The key benefit promoted by MEAP vendors is the ability to write code, often using a proprietary scripting language or well-established language like JavaScript. The code is then exported into native application platform code and can be distributed to other devices.
• 9.
  Metrics (vital factors/wins) Key Strategies ActionSteps Priority Mobile Product Development Goals 1. 2. 3. 4. Owners 30 60 90 5. Deploy mobile technology to 1,000 field staff Reduce paper document transactions by %25 the first year Reduce 30 minutes of data entry per person per day Reduce documentation errors by %25 the first year Target ROI within 12 months Identify inefficient processes in the field Receive feedback from key leaders in the field Launch 5% pilot program to field and evaluate feedback Executive buy-in Form the mobile product team Identify gaps in skill set Identify key development partner Identify team lead from user population Confirm budget with CFO John Paul Mary Jen Steve 2/1 2/15 2/1 2/12 2/15 3/1 3/15 3/1 3/13 4/1 4/15 4/1 4/12 MOBILIZING ENTERPRISE DATA 8 Project Action Plan Project Action Plans (PAP) are crucial to the success of your mobile implementation project. They help set priorities, define owners of tasks, and in general, outline expectations so that the entire project team is aware of the timeline for the final product release. Below is an example of a Project Action Plan for one portion of the project, which is product development. There could be a few of PAPs for different roles. For example, the development team could use their own PAP to identify key metrics, strategies, and action steps.
• 10.
  Metrics (vital factors/wins) Key Strategies ActionSteps Priority Mobile Product Development Goals 1. 2. 3. 4. Owners 30 60 90 5. MOBILIZING ENTERPRISE DATA 9
• 11.
  © InnoviMobile Designed bySpringboard – Marketing, Public Relations, Social Media InnoviMobile creates mobile applications for enterprise businesses across a broad range of industries. Let us help you get started today! 645.588.0011 ext.2 info@innovimobile.com innovimobile.com Written by Alex Zaltsman, CEO InnoviMobile