how to say yes to mobile...and avoid the top 10 career limiting mistakes

Download How to say Yes to Mobile...and Avoid the Top 10 Career Limiting Mistakes

Post on 17-Jul-2015

825 views

Category:

Technology

0 download

Embed Size (px)

TRANSCRIPT

Say yes to mobile

How To Say Yes to Mobileand Avoid the Top 10 Career-limiting Mistakes

William Clark, Global Vice President, Mobile Strategy

April 10, 2013

Watch On-Demand Replay Now

2013 SAP AG. All rights reserved.

#

1

Introduction: About the presenter

27 years industry experience including R&D at Ericsson, Texas Instruments, and mobile startups

Most recently, Research Vice President Gartner focused on mobile strategy, mobile app development, and context-aware computing

Quoted, interviewed in numerous publications worldwide, including Wall St. Journal, China Morning News, CNBC

Awarded patents in wireless software and industrial automation

William Clark SAP Global Vice President Mobile Strategy

Contact: william.clark@sap.com, @mobilebillclark

Watch On-Demand Replay Now

2013 SAP AG. All rights reserved.

#

About the Author:

William Clark, SAP Global Vice President Mobile Strategy

Past Experience,

27 years industry experience including R&D at Ericsson, Texas Instruments, and mobile startups,

Most recently, Research Vice President Gartner focused on mobile strategy, mobile app development, and context aware computing

Quoted, interviewed in numerous publications worldwide, including Wall St. Journal, China Morning News, CNBC

Awarded patents in wireless software and industrial automation

Contact: William.clark@sap.com, @mobilebillclark

2

State of the mainstream mobile market 2013

Innovators/Early Adopters

Mobile power users holistic approach

Refinement

Early Majority

Carefully planning mobile strategy

Still finding quick wins, embracing

Late Majority

Business teams driving mobile, not centralized

Focused on tactics, may not have MDM

Laggards

Mobile strategy is Dont ask, Dont tell

2013

2017

Alan Deeter, based on Geoffrey Moores Crossing the Chasm

Watch On-Demand Replay Now

2013 SAP AG. All rights reserved.

#

As you click, you can say that Mobile was just forming as an enterprise-wide requirement a few years ago (or whenever) and then click the mouse so the ball goes to the current state

3

Session purpose

Share foundational requirements for a successful mobile strategy

Without these in place, projects are hamstrung from the start

Walk through 10 career-limiting mistakes that can be avoided

Based on best practices, market feedback, and project experience

Here we should use an image that conveys the idea of 10 mistakes that could get you fired!

Watch On-Demand Replay Now

2013 SAP AG. All rights reserved.

#

4

The non-negotiables

A comprehensive mobile strategy

Executive-level sponsorship

Company-wide visibility

At minimum: a two-year vision for what you want to achieve the platforms, the scale, etc.

Tie employee-facing mobile strategy with market-facing strategy

Mobile deployment cant succeed as a departmental initiative

Alignment with the affected workforce

Credible BYOD approach

Focus groups, phased rollouts, app testing, and feature feedback

Communicate the overall plan acknowledge department/business unit investment

Watch On-Demand Replay Now

2013 SAP AG. All rights reserved.

#

This is a list of the must-haves and every successful program our customers have rolled out had these in common from the start. (talk about each of these for one minute)

Comprehensive mobile strategy: Users, Use Cases, device platforms, goals

Company wide visibility: The company should be involved in phased rollout of device support, application testing, so it is critical to set their expectations

Departments need to know what is/is not being covered in the mobile strategy to avoid rogue deployments

After you have this set of foundational requirements in place, there are still decisions that happen which can derail a program. Lets talk about the top ten failures and ways to avoid them

A comprehensive mobile strategy

At minimum: a two-year vision for what you want to achieve the platforms, the scale, etc.

Tie employee-facing mobile strategy with market-facing strategy

Executive-level sponsorship

Deploying mobile cant be successful as a departmental initiative

Company-wide visibility

Credible BYOD approach

Focus groups, phased rollouts, app testing and feature feedback

Communicate the overall plan acknowledge department/business unit investment

5

Mistake #1: Bring PC-era thinking to smartphone apps

How it happens: Pressure forces developers to port existing apps

Why it fails: Desktop application usability doesnt translate to device workflow

How to avoid it: Limit mobile apps to functionality the user needs; leverage tablets!

Watch On-Demand Replay Now

2013 SAP AG. All rights reserved.

#

How it happens

Pressure to get applications live force developers to take an existing app and just port it to a mobile platform

Why it fails

The usability of the application on a desktop does not translate to workflow and/or the small device screen leading to user frustration and lack of adoption

How to avoid it

Developers should consider what functionality the mobile user will need limit the mobile app to just that. Rethink business processes and dont overlook opportunities to leverage tablets. If necessary use mobile to complement PC/Web interfaces for more complex tasks.

6

Mistake #2: Letting back-end systems dictate innovation

How it happens: Too much time invested in back-end infrastructure

Why it fails: Successful mobile rollouts are quick-scaling and dynamic; back-end modifications delay and constrain functionality

How to avoid it: Mobile First or Mobile Only approach

Watch On-Demand Replay Now

2013 SAP AG. All rights reserved.

#

How it happens

When the team driving the mobile project is more knowledgeable and invests more time on the back-end systems, they allow infrastructure decisions to drive the scope, capabilities, or timing of their mobile programs

Why it fails

The rollout of a mobile program is dynamic, and if successful, scales quickly. Modifying back-end systems can be time consuming and risky. If back-end changes have priority, the development can be delayed and constrain the functionality to just a mobile window of the back-end

How to avoid it

Take a Mobile First approach to the business process. Use pace-layering techniques to deliver a new mobile app to users connected to the existing back-end. One test of success is if the users think that youve swapped out the back-end system!

7

Mistake #3: Wrong development methodology

How it happens: Developers apply methods for traditional apps to mobile apps

Why it fails: Waterfall development assumes lengthy, structured cycle; mobile requires agile development process

How to avoid it: Rethink development methodology, tools, and timelines for mobile deployment

Watch On-Demand Replay Now

2013 SAP AG. All rights reserved.

#

How it happens

Traditional application developers have a tried-and-true method for success which they naturally apply to mobile app development

Why it fails

Waterfall development assumes a lengthy and structured cycle for gathering requirements, building, testing, freezing code and rolling out an app

Mobile apps require an agile development process where that cycle is repeated every 2-4 weeks and the roll out of a static application never happens

How to avoid it

Development teams should examine their methodology and the tools that support it to ensure they can sustain a rapid build-test-refine-rollout-feedback cycle. Since traditional app deployment is much less complex and fluid, traditional app deployment timelines need to be re-thought.

8

Mistake #4: Try to do too much

How it happens: Developers bite off more than they can chew

Why it fails: New learning curves create setbacks and can lower confidence; gold-plating functionality causes impatience

How to avoid it: Enjoy a few quick wins; follow MVP (Minimal Viable Product) strategy

Minimum Viable Product Illustrated by Methodologist, torgoround.wodpress.com, Nov. 1, 2010, Adapted from the Featuritis Curve, Creating Passionate Users

Watch On-Demand Replay Now

2013 SAP AG. All rights reserved.

#

How it happens

As business places more demand on the mobile team, there is a possibility that developers bite off more than they can chew in the number of applications they can deliver, the richness of those applications, the underlying platform scalability, security, etc.

Why it fails

Until the mobile team has a solid foundation and delivery rhythm, every new learning can create a setback which lowers confidence

If the team gold-plates application functionality, or goes beyond the Minimum Viable Product, users (and senior management) will grow impatient

How to avoid it

Enjoy a few quick wins gather interest, demand, then deliver a little more follow MVP (Minimal Viable Product) strategy

While this may not be your standard approach, your executive team and your stakeholder community will appreciate the results

9

Mistake #5: Skillset gap

How it ha