How to Size a Mobile App Development Effort

6,528 views

Published on

Read more about this webinar and download the slides at: propelics.com/resources/webinar-how-to-size-a-mobile-app-development-effort/

Who should watch this webinar? Business and IT professionals looking to understand the components of mobile App development costs and how to estimate for a mobile App development effort.

Join Larry Lauvray, co-Founder of Propelics, to learn useful techniques and tips in sizing an Enterprise mobile App development effort. This webinar will cover how you should be thinking about a mobile app development effort, how size your mobile effort, the components that impact cost, and the process Propelics uses to size mobile app development projects.

In addition, you will learn:
* Decisions you will need to make that impact timeslines
* Resources and skills you need to support your mobile program
* The components of mobile App development costs
* How to contain the cost of your app development efforts
* The process Propelics uses to size mobile App development projects for our clients

How to Size a Mobile App Development Effort

  1. 1. Welcome.How to Size aMobile App @propelicsDevelopmentEffort Questions, Comments to #mobilestrategyJanuary 10th, 2013
  2. 2. Propelics Background – About Us • 15+ year track record • Fortune 500 clients • Global experience • 100% focused on mobile for the Enterprise • San Jose, Boston, PittsburghPropelics creates mobile strategies and world classApps for the Enterprise.Trusted by companies like yours: #mobilestrategy
  3. 3. What We Do• Enterprise Mobile Strategy Services Enterprise Mobile Strategy Mobile App Portfolio IT Readiness for Mobility BYOD and MDM Strategy Innovation through visualization Center of Excellence Creation• Mobile Advisory Services Mobile Mentoring Executive Education Speaking Engagements• Mobile App Development UX Design Onshore and Offshore App Development
  4. 4. Larry Lauvray: Propelics Co-Founder• Mobile Solution Architect - Hands-on mobile experience starting in 1990 - Custom applications since 1995 - Energy and Communications Industry ~9 years - Lead both business and technology segments• Enterprise Background • Enterprise solution architect ~22 years • Global application strategy and project delivery • Served over 30 industry verticals • Hundreds of custom and packaged application implementations 4 #mobilestrategy
  5. 5. Agenda• Trends and Challenges for Enterprise Mobile App Planning• Mobile Application Size and Cost Considerations Decisions you will need to make that impact timelines How to size mobile app development projects The components of mobile app development cost Resources and skills you need to support your mobile program How to contain the cost of your app development effort• Q&A Missed your topic? propelics.com/lets-talk
  6. 6. Q:What are the keyfactors that driveEnterprise MobileApp DevelopmentCosts? 6
  7. 7. Key Considerations - Enterprise Mobile App Dev Costs• What enterprise users am I targeting?• What mobile scenarios will be impacted?• What locations will the mobile app be used?• Will the mobile app be stand-alone ?• Will enterprise integration/authentication be required?• What device types and Operating Systems will be targeted? ….and many more including corporate culture 7
  8. 8. 8
  9. 9. Methods of customerinteraction will change Source: Morgan Stanley, 2011
  10. 10. Experiences are increasing usage and expectations #mobilestrategy
  11. 11. App Sizing
  12. 12. Mobile App Sizing Decisions What type of mobile user interactions? (informational, transactional, operational, collaboration, etc.) Which Devices per How many OS? (phone, tablet, Mobile screens in specialty device, the storyboard? etc.) Mobile Application Will the app work offline, Development synch, or need wireless Which Operating Planning Decisions Systems? (iOS, connectivity? Android, etc.) Will the app need enterprise Will the app leverage native (typical) system integration (data, rulescontrols or will custom interactions be engine, enterprise user necessary? authentication, etc.) #mobilestrategy
  13. 13. Sizing OverviewStep I: Step II: Step III:Scope Definition Baseline the timeframe, then adjust Final time, effort, effort within the time boxes and cost App Portfolio Finalize Culture of Critical path the timeline organization Mobile Segment the Interaction App and Finalize FTE flow into Flow and Integration effort and Screens Storyboard Complexity roles Time Baseline Multiple OS Apply hourly (1 Week/screen) and Device rates to the Market Types effort Opportunity Apply Effort Adjustments (Timeline and/or FTEs)
  14. 14. Create a Time Baseline: Per Your OrganizationBegin the baseline with a single/simple app with 1 FTE (then adjust effort): First time box = 25% of baseline25% App Visualization • Visualization- iteratively design the user and Prototype Stakeholder Buy- experience as a pixel- perfect prototype in Second time box = 50% of baseline Agile Mobile App • Build- assume a straightforward native50% Development Sprints mobile app in a native OS language (Java, Objective-C, etc.) Third timebox = 25% of baseline Q/A and • Verify- the app performs, meets user25% User Acceptance acceptance criteria, and is ready for store Submit for Store approval. Approval #mobilestrategy 14
  15. 15. Mobile App Development: Baseline Using 1 FTE App Visualization Agile Mobile App Development, Unit Testing, and Q/A with UAT – Q/A test planning – SME reviews Deployment assets and Prototype 2 Weeks 4 Weeks 2 Weeks (25%) (50%) (25%) 8 Screens = 8 Baseline Weeks (100%)Based on an average of deployed mobile apps – history teaches us toestimate 1 week per screen for a simple baseline (minimum 3 weeks) • Approximate 25% + 50% + 25% timeline allocation (assume 1 FTE)Then apply adjustment factors (part art, part science): • Organizational culture and existing governance processes • Existing Enterprise SDLC adjusted for mobile (speed and agility) • Multiple mobile device types or Operating Systems take more FTEs • Integration for mobile closely matches typical enterprise integration • Maturity of business rules and data match existing enterprise effortsNote: Several roles will fill the 1 FTE baseline (UX designer, Developer, etc.) #mobilestrategy 15
  16. 16. Adjust the Baseline – Per Your Organization Adjust time and effort 2 WeeksApp Visualization + Time Impact Itemand Prototype Adjustment +/- 1 Wk. Corp. Culture and Focus n/a Add Integration (reuse 4 Weeks will vary) + FTE Effort Adjustment n/a Add app on/offline synch Agile Mobile App Development +1 Wk. Add dynamic content or business rules +1 Wk. Add an OS 2 Weeks +1 Wk. Specialty branding (or first mobile app) Q/A with UAT – Deployment assets Submit for Store Approval #mobilestrategy 16
  17. 17. Adjust the Baseline – Per Your Organization Adjust time and effort 2 WeeksApp Visualization Impact Itemand Prototype +/- 2 Wk. Corp. Culture and Focus 2 FTE Wk. Add Integration (reuse 4 Weeks (varies) will vary) + FTE Effort Adjustment +1 Wk. Add app on/offline synch Agile Mobile App Development +2 Wk. Add dynamic content or (varies) business rules 2x effort Add an OS* 2 Weeks n/a Specialty branding (or first mobile app) Q/A with UAT – Deployment assets Submit for Store *Note: Approval MADP considerations if 2+ Operating systems. Expect 50-70% code reuse during development but testing effort will still be 2x 17
  18. 18. Adjust the Baseline – Per Your Organization Adjust time and effort 2 WeeksApp Visualization Impact Itemand Prototype +/- 2 Wk. Corp. Culture and Focus 1 Wk. per Add Integration (reuse 4 Weeks (varies) will vary) + FTE Effort Adjustment +1 Wk. Add app on/offline synch Agile Mobile App Development +1 Wk. Add dynamic content or (varies) business rules 2x effort Add an OS* 2 Weeks n/a Specialty branding (or first mobile app) Q/A with UAT – + Time Deployment assets Adjustment + FTE Effort Adjustment *Note: MADP considerations if 2+ Operating systems. Expect 50-70% code reuse during development but testing effort will still be 2x 18
  19. 19. Example Components
  20. 20. App Planning: Create the Storyboard• Iterative approach can be device/OS agnostic – refine over time• The screen groups, data, wireless, and integrations become clear #mobilestrategy 20
  21. 21. App Decisions based on Storyboard Learnings What type of mobile user interactions? (informational, transactional, operational, collaboration, etc.) How many Which Devices perMobile screens in OS? (phone, tablet, the storyboard? specialty device, ~8 etc.) Mobile Application Will the app work offline, Development synch, or need full online Which Operating Planning Decisions Systems? (iOS, wireless connectivity? Android, etc.) Will the app leverage native (typical) Will the app need enterprisecontrols or will custom interactions be system integration (data, rules necessary? engine, enterprise user authentication, etc.) 21
  22. 22. App Planning and Development Project ManagementStoryboard Visualization User Q/A Application Experience Build/Test Scope Iterations Architecture UAT Deploy and support 22
  23. 23. App Planning and Development Project ManagementStoryboard Visualization User Q/A Application Experience Build/Test Scope Iterations Architecture UAT 25% Deploy and support 23
  24. 24. Visualization and Prototype App Concept Wireframe Visual Design 25% of the Mobile Application Cost Visualization Visualize the concept  Plan the “Experience” Finalize prior to Development (multipliers): • Number of Screens User • Screen flow and Types of controls Experience • Navigation Gestures • Pop-over and text layout Architecture • OS versions and device resolutions 24
  25. 25. App Planning and Development Project ManagementStoryboard Visualization User Q/A Application Experience Build/Test Scope Iterations Architecture UAT 50% Deploy and support 25
  26. 26. Development – Agile Build and Test Agile Development Plan:  Build Agile Stories  Weight the story effort  Baseline development capacity (FTEs)  Assign stories to sprints  Create task backlog  Measure and adjust 50% of the Effort and Cost • Design the MVC: • Model: How the app behavesBuild/Test • View: Screen behaviorIterations Q/A • Controller: Manages Input/Output • Local Database design • Security, Encryption, Authentication • Data and Business rule dependencies • Hardware versus Software controls 26
  27. 27. App Development: Q/A and Acceptance Project ManagementStoryboard Visualization 25% User Q/A Application Experience Build/Test Scope Iterations Architecture UAT Deploy and support 27
  28. 28. Development – Quality Assurance and User Acceptance Mobile Simulators Mobile Testing Plans:  Leverage Agile Stories  Business Scenarios  Positive and Negative tests Physical mobile devices  Integrated rules and data  Break Tests, Memory failure  Timeout, Wireless, Gestures  Verify UX standards, Resolution 25% of the Effort and Cost • Number of Screen (test flow & combinations) Q/A • Types of controls (custom = testing risk/effort) • Synch/Offline (iterative wireless scenario tests) • Enterprise Integration and Security UAT • Enterprise business rules and data User Authentication (with failure) • Native OS, test screen resolutions (iPad) 28
  29. 29. Mobile App Development Example: Use Case EffortKickoff Submit for Store 8 Weeks Approval App Visualization and Prototype Mobile App Development, Unit Testing, and Q/A test planning – SME reviews 2 Weeks Q/A with User Acceptance – 4 Weeks Deployment assets 2 Weeks 1.5 FTEs: 2 FTEs: 2.5 FTEs: • UX architect (Full Time) • Developer (Full Time) • Tester (Full Time) • Mobile Architect (PT) • Integration architect (PT) • Developer (PT) • Mobile Architect (PT) • Integration architect (PT) • Mobile Architect (PT) $12k* $32k* $20k* *Note: Assume $100/hr. (average) #mobilestrategy 29
  30. 30. Tips for Reducing Risk, Cost, and Time• Prototyping is the best investment of the project. Spend the time you need to get stakeholder feedback and make updates. - This will reduce the overall development risk and effort related to changes• Create a clickable/installable prototype if expectations are not aligned. - The iOS Storyboard feature allows for ~98% reuse of the screen mockups• Application architecture using the Model, View, Controller standards will ensure scalability, stability, and ease of maintenance.• As with other enterprise applications: - Create an enterprise steering committee to make the tough business/technical decisions – or leverage the mobile COE for escalations - Strong thought leadership from the business will ensure better work products (Prototype, Application architecture, and User Acceptance) 30
  31. 31. Tips for Reducing Risk, Cost, and Time (2)• Build heavy data processing, business rules, and shared logic into the host applications or integrations rather than using the mobile processor - This ensures enterprise consistency, reuse, and mobile app performance - Business rule changes can be implemented without deploying app updates• Plan for immediate user feedback after rollout – expect to deliver enhancements and fixes in a quick follow-up phase. - This will reduce user adoption barriers and enhance the community opinion• Clearly outline the devices and OS versions that are supported. - Android fragmentation inherently creates testing and acceptance risk• For internal MDM deployments, ensure the targeted users have pre- registered all devices - Desire for the app can drive MDM adoption, so message timing is critical 31
  32. 32. Tips for Reducing Risk, Cost, and Time (3)• Use experienced and senior resources for leadership roles: - User Experience Architect: Photoshop, CSS3 - iOS: Objective-C, Xcode - Android: Java, C, C++, Eclipse - BlackBerry: Java, Eclipse - Windows Mobile: C, C++, Visual Studio - Web: JavaScript, HTML5, CSS3, (jQuery mobile, Sencha, etc.) - MADP: Most use JavaScript as the basis - Integration: JSON, REST, XML• Use cross-platform tools in specific instances - Plan to deploy to multiple OS platforms (2+) - Core in-app logic is complicated (the model or controller) - Note that the (view) screens will need a separate effort per OS deployment - JavaScript skills available rather than native platform architects - 32
  33. 33. Thanks for your Time• Mobile application – ongoing support - Mobile users expect quicker turnaround than typical enterprise apps - User feedback will be immediate - Plan to capture and prioritize the feedback - Ideas, Issues, and Enhancements - Assign a product manager as a primary point of contact - Retain the skeleton development team for the quick-release enhancements• In Conclusion: - Storyboard the interaction flow - Create the time baseline + adjust the time/effort - Begin the mobile SDLC - Visualization and usability iterations - Iteratively build the App and Integrations - Enterprise testing and acceptance - Ongoing Support 33
  34. 34. Propelics Kickstarts Special Offer 20 Hours of mobile advisory services Mobile App with the purchase of Rapid a Prototype Kickstart Prototype Kickstart info@propelics.com 888-405-2820 Mobile App MDM/BYOD Mobile IT Readiness Prototype Roadmap Kickstart Center of for Mobile Factory Excellence Kickstart 34
  35. 35. • Innovation Focus• Engaging Process• Mobility Centric• Experience Across Industries• Enterprise Solutions• Advisors, Strategists, Implementers• Strategy at the Pace of Mobility
  36. 36. Thank you

×