How to Size a Mobile App Development Effort

Welcome.@propelics

Questions, Commentsto #mobilestrategy

How to Size a Mobile App DevelopmentEffort

January 10th, 2013

Propelics Background – About Us

• 15+ year track record

• Fortune 500 clients• Global experience• 100% focused on

mobile for the Enterprise

• San Jose, Boston, Pittsburgh

Propelics creates mobile strategies and world class Apps for the Enterprise.

Trusted by companies like yours:

#mobilestrategy

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 ServicesMobile Mentoring

Executive Education

Speaking Engagements

Mobile App DevelopmentUX Design

Onshore and Offshore App Development

Mobile App Architecture

Prototype Factory

What We Do

Larry Lauvray: Propelics Co-Founder

4

• 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

#mobilestrategy

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

Q:What are the key factors that drive Enterprise Mobile App Development Costs?

6

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

Methods of customer interaction will change

Source: Morgan Stanley, 2011

Experiences are increasing usage and

expectations

#mobilestrategy

App Sizing

Mobile ApplicationDevelopment

Planning Decisions

Will the app leverage native (typical) controls or will custom

interactions be necessary?

How many Mobile screens in the storyboard?

Which Operating Systems? (iOS, Android, etc.)

Which Devices per OS? (phone, tablet, specialty

device, etc.)

What type of mobile user interactions? (informational, transactional, operational,

collaboration, etc.)

Will the app need enterprise system integration (data,

rules engine, enterprise user authentication, etc.)

Will the app work offline, synch, or need wireless connectivity?

Mobile App Sizing Decisions

#mobilestrategy

Sizing Overview

App Portfolio

Segment the flow into Screens

App and Integration Complexity

Market Opportunity

Mobile Interaction Flow and

Storyboard

Apply hourly rates to the

effort

Finalize FTE effort and

roles

Culture of the

organization

Multiple OS and Device

Types

Finalize Critical path

timeline

Step I: Scope Definition

Step II: Baseline the timeframe, then adjust effort within the time boxes

Step III: Final time, effort, and cost

Time Baseline

(1 Week/screen)

Apply Effort Adjustments(Timeline and/or FTEs)

14

App Visualization and Prototype

Agile Mobile App Development Sprints

Q/A and User Acceptance

Submit for Store Approval

Create a Time Baseline: Per Your Organization

First time box = 25% of baseline• Visualization- iteratively design the

user experience as a pixel- perfect prototype

Second time box = 50% of baseline• Build- assume a straightforward

native mobile app in a native OS language (Java, Objective-C, etc.)

Third timebox = 25% of baseline• Verify- the app performs, meets user

acceptance criteria, and is ready for store approval.

Begin the baseline with a single/simple app with 1 FTE (then adjust effort):

Stakeholder Buy-in

25%

50%

25%

#mobilestrategy

15

8 Screens = 8 Baseline Weeks (100%)


2 Weeks(25%)

Agile Mobile App Development, Unit Testing, and Q/A test planning – SME

reviews

Q/A with UAT – Deployment assets

4 Weeks(50%)

2 Weeks(25%)

Mobile App Development: Baseline Using 1 FTE

Based on an average of deployed mobile apps – history teaches us to estimate 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 efforts

Note: Several roles will fill the 1 FTE baseline (UX designer, Developer, etc.)

#mobilestrategy

16


2 Weeks


2 Weeks


Adjust the Baseline – Per Your Organization

Adjust time and effort

Impact Item

+/- 1 Wk. Corp. Culture and Focus

n/a Add Integration (reuse will vary)

n/a Add app on/offline synch

+1 Wk. Add dynamic content or business rules

+1 Wk. Add an OS

+1 Wk. Specialty branding (or first mobile app)

+ Time Adjustment

Agile Mobile App Development

4 Weeks + FTE Effort Adjustment

#mobilestrategy

17


2 Weeks



2 Weeks


4 Weeks


Impact Item


2 FTE Wk.(varies)

Add Integration (reuse will vary)

+1 Wk. Add app on/offline synch

+2 Wk.(varies)

Add dynamic content or business rules

2x effort Add an OS*

n/a Specialty branding (or first mobile app)

*Note: MADP considerations if 2+ Operating systems. Expect 50-70% code reuse during development but testing effort will still be 2x


+ FTE Effort Adjustment

18


2 Weeks


2 Weeks



Impact Item


1 Wk. per(varies)

Add Integration (reuse will vary)

+1 Wk. Add app on/offline synch

+1 Wk.(varies)

Add dynamic content or business rules

2x effort Add an OS*

n/a Specialty branding (or first mobile app)

*Note: MADP considerations if 2+ Operating systems. Expect 50-70% code reuse during development but testing effort will still be 2x

+ Time Adjustment

+ FTE Effort Adjustment


4 Weeks + FTE Effort Adjustment

Example Components

App Planning: Create the Storyboard

20

• Iterative approach can be device/OS agnostic – refine over time• The screen groups, data, wireless, and integrations become clear

#mobilestrategy

Mobile ApplicationDevelopment

Planning Decisions

Will the app leverage native (typical) controls or will custom

interactions be necessary?

How many Mobile screens in the storyboard?

~8

Which Operating Systems? (iOS, Android, etc.)

Which Devices per OS? (phone, tablet, specialty

device, etc.)

What type of mobile user interactions? (informational, transactional, operational,

collaboration, etc.)

Will the app need enterprise system integration (data,

rules engine, enterprise user authentication, etc.)

Will the app work offline, synch, or need

full online wireless connectivity?

App Decisions based on Storyboard Learnings

21

App Planning and Development

22

ApplicationScope

Visualization

Architecture

Build/TestIterations

UAT

User Experience

Project Management

Deploy and support

Q/A

Storyboard


23

ApplicationScope

Visualization

Architecture


UAT

User Experience

Project Management

Deploy and support

Q/A

Storyboard

25%

Visualization and Prototype

24

25% of the Mobile Application CostVisualize the concept Plan the

“Experience”

App Concept Wireframe Visual Design

Visualization

Architecture

User Experience

Finalize prior to Development (multipliers):• Number of Screens• Screen flow and Types of controls• Navigation Gestures• Pop-over and text layout• OS versions and device resolutions


25

ApplicationScope

Visualization

Architecture


UAT

User Experience

Project Management

Deploy and support

Q/A


Storyboard

50%

26

Development – Agile Build and Test

Agile Development Plan:Build Agile StoriesWeight the story effortBaseline development

capacity (FTEs)Assign stories to sprintsCreate task backlog Measure and adjust

Build/TestIterations Q/A

50% of the Effort and Cost• Design the MVC:

• Model: How the app behaves• View: Screen behavior• Controller: Manages Input/Output

• Local Database design• Security, Encryption, Authentication• Data and Business rule dependencies• Hardware versus Software controls

App Development: Q/A and Acceptance

27

ApplicationScope

Visualization

Architecture


UAT

User Experience

Project Management

Deploy and support

Q/A

Storyboard25%

28

Development – Quality Assurance and User Acceptance

Mobile Testing Plans:Leverage Agile StoriesBusiness Scenarios

Positive and Negative tests Integrated rules and data

Break Tests, Memory failureTimeout, Wireless, GesturesVerify UX standards, Resolution

25% of the Effort and Cost• Number of Screen (test flow & combinations)• Types of controls (custom = testing risk/effort)• Synch/Offline (iterative wireless scenario tests)• Enterprise Integration and Security

• Enterprise business rules and data User Authentication (with failure)

• Native OS, test screen resolutions (iPad)

Mobile Simulators

Physical mobile devices

UAT

Q/A

29

8 Weeks


2 Weeks

Mobile App Development, Unit Testing, and Q/A test planning – SME reviews

Q/A with User Acceptance – Deployment assets4 Weeks

2 Weeks

Kickoff Submit for Store Approval

Mobile App Development Example: Use Case Effort

1.5 FTEs:• UX architect (Full Time)• Mobile Architect (PT)

2 FTEs:• Developer (Full Time)• Integration architect (PT)• Mobile Architect (PT)

2.5 FTEs:• Tester (Full Time)• Developer (PT)• Integration architect (PT)• Mobile Architect (PT)

$32k*$12k* $20k*

*Note: Assume $100/hr. (average)#mobilestrategy

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)

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

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

-

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

-

Propelics Kickstarts

Mobile App

Roadmap

MDM/BYOD

Kickstart

Mobile Center of

Excellence

IT Readiness for Mobile Kickstart

Prototype Factory

34

Mobile App

Rapid Prototyp

e Kickstart

Special Offer

20 Hours of mobile advisory services with the

purchase of a Prototype Kickstart

[email protected]

888-405-2820

Innovation FocusEngaging ProcessMobility CentricExperience Across IndustriesEnterprise SolutionsAdvisors, Strategists, ImplementersStrategy at the Pace of Mobility

Thank you

Documents

How to Size a Mobile App Development Effort