Successfully reported this slideshow.
Your SlideShare is downloading. ×

Enterprise Mobile Strategy Framework - I

Loading in …3

Check these out next

1 of 31 Ad

More Related Content

Slideshows for you (19)

Similar to Enterprise Mobile Strategy Framework - I (20)


Recently uploaded (20)

Enterprise Mobile Strategy Framework - I

  1. 1. Enterprise Mobile Strategy Framework – I
  2. 2. Webinar Overview Lay the framework for a robust Enterprise Mobile Strategy. Overcome the challenges of Enterprise Mobility and seize the opportunities in transforming your organization. Take a holistic view of the Enterprise wide Mobility needs.
  3. 3. Agenda • Company & Speaker Intro • Enterprise Mobility Drivers • Mobility Maturity Assessment • Design Thinking & Roadmap • Build vs Buy • Mobility Governance & Policies • BYOD/Device Strategy • Native apps vs Hybrid vs HTML5 • Q&A
  4. 4. Target Audience • IT Executives • IT Architects • SAP, Oracle EBS, People soft, JDE customers • Business: Sales, Service, Customer support, Supply Chain, Procurement, Manufacturing, HR, Logistics, and Finance.
  5. 5. Speaker Bio – Raj Peddisetty • Digital Transformation advisor and a seasoned practitioner of Design Thinking, User Experience in Mobile, Ecommerce, Cloud and Marketing automation. • 11 years of experience in SAP, Oracle for industries ranging from Wholesale, Retail to Manufacturing and Healthcare. • Experience: consultant, architect, developer for system integrators such as IBM, Accenture, Cap Gemini, SAP, CSC. • Global business transformation projects for Fortune 500 clients. • MBA from the University of Chicago Booth School of Business and is certified in Design Thinking by IDEO.
  6. 6. ▪ An Award winning Enterprise Mobility Solutions provider ▪ Prebuilt suite of 100+ Mobile Apps to solve complex business problems ▪ Serving Fortune 1000 customers across industries ▪ Elite team with expertise in Business Process, User Experience & Design Thinking ▪ Global presence across US & India 50+ Mobile Projects 75 people 4 years in business 300+ Technical Interfaces Top 20 of the global enterprise mobility firms Google Mobile App Challenge winner About Algarytm
  7. 7. Objective Put together a robust but adaptable Enterprise Mobile Strategy Framework by taking a holistic view of an organizations mobility needs.
  8. 8. Why Strategy? Poor ROI Re-writing of apps Maintenance Challenges Hard to hire, and retain talent
  9. 9. Mobility Drivers • Smartphone penetration • BYOD • Mobile workforce – Service, sales, Supply Chain, Customers • Availability of Devices, connectivity. • Demand for agility. • Demand for real-time information, decision making.
  10. 10. Taking whatever SAP, Oracle, or IBM is offering is not a strategy
  11. 11. Free Apps from SAP and Oracle have more hidden costs and results in expensive customization and maintenance.
  12. 12. Maturity Assessment
  13. 13. Capabilities None Early/Adhoc Intermediate Advanced Transformative Strategy & Roadmap Business Mobile Policy Development Budget Governance MDM Security Device Policy Architecture UX Strategy App Development App Testing App Maintenance Maturity Levels Infra Enablement Organization Enablement Business Enablement OVERALL
  14. 14. Roadmap Design Design Thinking workshops help you understand what people really need. Prioritize Prioritize apps based on Business value, technical feasibility, and complexity. Estimate Estimate ROI and put together a road map.
  15. 15. Design Thinking – Do business in new and better ways
  16. 16. Design Thinking Workshop Outcomes • Overall high level requirements. • Prioritization based on value. Ex. Sales apps have more value than backoffice apps. • Weighted matrix w/ Technical feasibility, returns(Value), cost, etc. • Wireframes – Iterate, test, and incorporate feedback.
  17. 17. Roadmap - Outcomes • Put together the complete list of apps need to be developed. • Establish timeline, high level budget, time, resources. • Helps building a robust Mobility Strategy that could be part of a cohesive Digital Strategy.
  18. 18. BYOD/Device Strategy • 3 types of users: • Executives – Tablet users • Employees/Customers – any smartphone/tablet. • Field workers who use rugged devices. • Providing your own devices is expensive and need to budget for maintenance. • BYOD needs strict policies to secure and manage devices and Data. • Ruggedizing is another cheaper alternative.
  19. 19. Rugged Device Strategy • Expensive but durable. • Capabilities: Credit card reader, high duty bar code scanner, compliance with industry regulations, long battery life, etc. • With Android, UX is similar to Smart Devices running iOS, Android. • Strongly recommended for Field Service, Warehouse and plant maintenance type of workers.
  20. 20. Mobility Governance • Unique challenges <-- Business Process + App Dev + Infra + Ops • Setup a COE of Legal, IT, and Business. • Establish a charter. • COE could report to the CIO. • Setup roles and responsibilities.
  21. 21. Mobility Governance Policies • How do you protect data? • What apps have to be restricted? • If company offers data plan reimbursements, can employees use this for personal apps? • Does the company offer support for personal devices? • Policies, agreements, and consent from employees is tricky. • Privacy policies, usage policies need to be in place.
  22. 22. Airwatch recommends a 3 step strategy
  23. 23. Buy vs Build: Buying Off the shelf apps PROs: • Quick go to market. • Continued innovation • Saves tons of money on design, development and maintenance CONs: • You need to pay License fee. • Sometimes lack flexibility • Some vendors force platforms and restrictions. • Some vendors lack comprehensive solution offering.
  24. 24. Buy vs Build: Building the apps PROs: • Tailor made custom apps CONs: • Take enormous amounts of time and resources to build 20+apps. • Needs wide variety of skills. • Takes longer to execute CAPRIZA Could be a potential platform to alleviate many of the Build issues.
  25. 25. Buy vs Build: Our recommendation Research the solution providers with a comprehensive strategy towards Enterprise Mobility. You need a full suite of apps, services for a quick journey towards Digital Transformation. Take a holistic enterprise wide look.
  26. 26. Native vs Hybrid vs HTML5 Native Apps: • Native apps offers the ultimate UX. • Is appropriate for any scenario but are too expensive to build, maintain across platforms. • For cross platform apps, Xamarin is a best fit. • Leverages all device functionality. Scenarios: Offline apps Consumer facing apps. Revenue generating ecommerce apps. UX, branding and reputation are key.
  27. 27. Hybrid Apps • Balances between Native and HTML5 apps in functionality, development time, and costs. • No compromise on leveraging device features. • But UX is not as smooth as Native apps. Scenarios: • UX is not critical. • One set of code to serve all major platforms. • Could support offline apps as well. Native vs Hybrid vs HTML5
  28. 28. HTML5 apps • Supports online only scenarios. • UX is not as great as Native apps. • Supports 70% to 80% of the use- cases. Scenarios: • Internal Employee facing Productivity apps, transactional apps. • Examples: HR, Finance and Customer support apps. Native vs Hybrid vs HTML5
  29. 29. Q&A
  30. 30. Next Webinars Framework for building a robust Enterprise Mobile Strategy – Part II Robust Enterprise Mobile Strategy with Capriza.
  31. 31. Follow us on Our Contact Coordinates Algarytm 17772 Preston Rd, Dallas, TX 75252 Address Email Website Contact Number 318-235-5720 Stay in Touch