Making Leaders SuccessfulEvery Day
The Evolution of "Mobile First"DevelopmentJeffrey Hammond, Principal AnalystSeptember 26, 2012
Mobile is the new face of                                                                                        engagemen...
It’s becoming a BYOT world
This creates real differences for IT shopsApplications: Java EE, .NET, Flash   Objective C, Java, HTML5, WinRT    Devices:...
Are you ready?   Are you Agile enough?                               Do you collect (and incorporate)                     ...
Assemble small, focused development teams•  Plan for smaller teams (3-6), and more of them•  Scrum, and “Scrum of Scrums” ...
Native Apps Argue For Cross Training                         Shared, Cross Team Roles      Product Owner/PM          Desig...
Favor simpler ALM processes•  Fewer branches in SCM – evolve toward DVCS•  Use visual designs and prototypes instead of te...
Building apps changes the dev life cycle    Lifecycle Focus                         Systems of    Time to Feedback    Enga...
Adapting Agile principles•    Kanban boards help manage atomic demand•    Use wireframes to drive feedback and build backl...
IdentifyA Multi-channel Journey Map                                            customer and                               ...
Prioritize gathering user feedback•  Collect feedback early and often•  Assign someone to listen to public feedback•  Anal...
Balance release speed with a focus on quality•  Initial quality is important – due to app store curation•  Expedited relea...
A Typical Mobile App Release ScheduleFeatures +                                                            V 2.1Defect fix...
Your technology choices matter                          Hybrid         Pixel-perfect                  Cost         Experie...
A simple guide for technology decisions Think about the workloads you are automating…                         HybridNative...
The gaps between strategies are shrinking                    HybridNative         Mixed Mode Middleware                Web...
Modern mobile apps: Evolving Infrastructure   3x3 strategies for building mobile apps                                     ...
Middleware vs. rolling your own backend• Labor costs vs. capital costs• Do you have mixed mobile workloads?• Is infrastruc...
The future of mobile is context – dropyour “mini-PC” mindset nowWith new sensors, yourphone will know moreabout you than a...
Opportunities for context will increase                               Technology                                          ...
Mobile is moving fast – and gettingfaster•  Mobile devices are the biggest shock to your world   since the introduction of...
Sriram RamanathanCTOKony Solutions, Inc.
The	  KonyOne	  Mul5	  Channel	  PlaLorm	               Write	  Once	                                                  Bui...
Mul5	  Channel	  PlaLorm	                                                       SMART	  PHONE	                            ...
QUESTIONS?          More information on www.kony.com/resources          www.kony.com          Twitter: @konyCopyright	  ©	...
Upcoming SlideShare
Loading in …5
×

Kony-Forrester Webinar: The Evolution of Mobile First Development

1,085 views
868 views

Published on

Forrester's Jeffrey Hammond talks strategy on how to organize your dev team around an increasingly mobile enterprise.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,085
On SlideShare
0
From Embeds
0
Number of Embeds
16
Actions
Shares
0
Downloads
56
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Kony-Forrester Webinar: The Evolution of Mobile First Development

  1. 1. Making Leaders SuccessfulEvery Day
  2. 2. The Evolution of "Mobile First"DevelopmentJeffrey Hammond, Principal AnalystSeptember 26, 2012
  3. 3. Mobile is the new face of engagement 9/11 1.3 M+ Android activations per day, 500 million+ total devices 9/12 400 M+ iOS devices sold to date Are you ready for the Mobile Shift? Source: Flickr (http://www.flickr.com/photos/sashawolff/3793206523/sizes/l/)3 Entire contents © 2010 Forrester Research, Inc. All rights reserved.
  4. 4. It’s becoming a BYOT world
  5. 5. This creates real differences for IT shopsApplications: Java EE, .NET, Flash Objective C, Java, HTML5, WinRT Devices: Company-provided Employee-owned Security: Locked down Zero-trustProvisioning: IT push App store pull Life cycle: Three to four years 12 to 18 months
  6. 6. Are you ready? Are you Agile enough? Do you collect (and incorporate) rapid feedback? Can you design useful, usable, desirable experiences? Can you build high quality, 5 star apps?Source: Flickr (http://www.flickr.com/photos/kaz25/2444344463/sizes/o/in/photostream//)
  7. 7. Assemble small, focused development teams•  Plan for smaller teams (3-6), and more of them•  Scrum, and “Scrum of Scrums” are a good starting model•  If you go native specialize developers w/ technology•  Hire design talent, and invest in information architecture•  QA + security is everyone’s job – retire the QA center of excellence•  APIs everywhere, all the time•  Downsize your sourcing strategies
  8. 8. Native Apps Argue For Cross Training Shared, Cross Team Roles Product Owner/PM Design Team Scrum Master/ProjM iOS Dev Team Android Dev Team Web Dev TeamLead iOS Dev Lead Android Dev Lead Web Dev Android Dev Web Dev iOS Dev Cross-train Cross-train Cross-train
  9. 9. Favor simpler ALM processes•  Fewer branches in SCM – evolve toward DVCS•  Use visual designs and prototypes instead of textual requirements•  Emulators and On-device testing mean more hands on developer time•  CI becomes decentralized, more atomic, and critical•  Test like you deploy – the last mile may be public and beyond your control•  Mocks and mocking tools help manage multi layer complexity
  10. 10. Building apps changes the dev life cycle Lifecycle Focus Systems of Time to Feedback Engagement Systems of Time to Certainty Record Systems of Time to Safety Operation
  11. 11. Adapting Agile principles•  Kanban boards help manage atomic demand•  Use wireframes to drive feedback and build backlog•  Use visual prototypes to gather “broad brush” feedback•  Develop personas to drive insight into user behavior•  Think about “contextual” design•  Employ journey maps to understand multi-channel usage patterns
  12. 12. IdentifyA Multi-channel Journey Map customer and stages of journey Persona: James Awareness Consideration Research Purchase Engagement Wow Describe each step in the journey, the customer’s needs andEnjoyable perceptionsFunctional 11 Indicate significant steps 10 Neutral Missed It Indicate primary (and secondary ) devices forFrustrating each step
  13. 13. Prioritize gathering user feedback•  Collect feedback early and often•  Assign someone to listen to public feedback•  Analyze feedback for recurring patterns of failure and opportunity•  Proactively reach out to unhappy users•  Build feedback and analytic systems into your applications•  Ask for positive reinforcement•  Create a regimen of A/B testing
  14. 14. Balance release speed with a focus on quality•  Initial quality is important – due to app store curation•  Expedited releases are no substitute for real testing•  “Blue/Green” environments complement A/B testing approach•  Deployment and feedback management tools grow in importance•  Simultaneous release across clients is important•  Avoid patches – bundle bugfixes with new features•  Don’t wait for GA – use platform betas•  Moves to organic releases that meet user and market demands
  15. 15. A Typical Mobile App Release ScheduleFeatures + V 2.1Defect fixes V 2.0 V 1.2.1 V 1.2.2 V 1.2 V 1.0 (MVP) New OS version Regression + Emergency released Patch Regular Internal Sprint Cycle + Beta Testing (2 weeks) Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
  16. 16. Your technology choices matter Hybrid Pixel-perfect Cost Experience EffectiveNative Web Maximum Frequent Performance Updates Middleware
  17. 17. A simple guide for technology decisions Think about the workloads you are automating… HybridNative Web Middleware
  18. 18. The gaps between strategies are shrinking HybridNative Mixed Mode Middleware Web WebGL IndexedDB Device API Middleware
  19. 19. Modern mobile apps: Evolving Infrastructure 3x3 strategies for building mobile apps HybridMobile Clients Web NativeService Infrastructure Public Cloud Middleware Roll-your-own Server Backend BaaS On-premises/Private CloudSystems of Record LDAP/IAM SCM LOB 1 LOB N CRM
  20. 20. Middleware vs. rolling your own backend• Labor costs vs. capital costs• Do you have mixed mobile workloads?• Is infrastructure control important?• How cutting edge are your needs?• How skilled is your development team?• How complex are your integration needs?• What testing resources do you have?• How fast do you need to move?
  21. 21. The future of mobile is context – dropyour “mini-PC” mindset nowWith new sensors, yourphone will know moreabout you than anyone oranythingConsumer demand forconvenience will killprivacy BIG MOTHER IS HERE TO HELP http://www.flickr.com/photos/22320444@N08/4272283260/sizes/m/ YOU
  22. 22. Opportunities for context will increase Technology Opportunity (examples) • Distance measured, gesture controlControls • 3D cameras • Biometrics • Security, access cards, ID • Conversational voice recognition • Verbal command (e.g., Siri) • Near Field Communications (NFC) • Payments, ticketing, and information • Augmented reality, video outputDisplays • 3D displays • High-resolution displays • Media consumption, bar codes • Micro-mirrors • Image projection; pico-projectors • Touch inputs (fine-tuned)Data collection •  Accelerometers (detects motion/tilt) •  Phone orientation as control, pedometer • Chemical sensors • CO detection, food freshness • Gyroscopes • Gesture control, navigation, games • Magnetometers • Directions – “Is it over there?” • Microbolometers (infrared) • Night vision; heat; light/dark • Pressure sensor • Height in buildings Source: A.M. Fitzgerald & Associates, Yole Développement, and interviews with Atmel, InvenSense, and Sharp Electronics
  23. 23. Mobile is moving fast – and gettingfaster•  Mobile devices are the biggest shock to your world since the introduction of the PC•  Enterprise mobile is collapsing into a consumer based, BYOT reality – a mobile first reality•  You must push your development organization to get faster, and more flexible to compete•  You need multiple approaches to support mobile workloads, and the infrastructure to integrate it•  Do you want to spend your time building infrastructure, or building apps?•  Mobile context will enable breakthrough experiences – if you are ready to take advantage of them
  24. 24. Sriram RamanathanCTOKony Solutions, Inc.
  25. 25. The  KonyOne  Mul5  Channel  PlaLorm   Write  Once   Build  Everywhere     Run  Everywhere   A  single  code  base   MOBILE   NATIVE  SUPPORT  FOR  8  OSs   TABLET   WEB  SUPPORT-­‐  Mobile  and  Desktop   •  Individual,  device  op5mized  sites   •  Basic  HTML  >>  HTML5   Single  Page   HTML  5   Architecture   DESKTOP  WEB   Standard   HTML  4   Hybrid   Mixed  Mode   Kony  MESSAGING  SERVICES   KIOSK  &  DESKTOP  NATIVE     Win32  and  Win8  Copyright  ©  2012  Kony  Solu5ons,  Inc.    CONFIDENTIAL   25   25  
  26. 26. Mul5  Channel  PlaLorm   SMART  PHONE   TABLET   WIN  32/Win  8  DESKTOP   KIOSK   FEATURE  PHONE   DESKTOP  WEB  CHANNELS   ON-­‐DEVICE  APP  CONTAINER   ON-­‐DEVICE  APP    STORE     NaOve   Mixed  Mode   Web  –  Mobile  and  Desktop   HTML5   iOS   Windows  Phone   §  Mix  and  match  HTML5  and  Na5ve  code  on  TECHNOLOGIES   form  by  form  basis   Basic  HTML     Android   Blackberry   §  Leverage  na5ve  capabili5es    and  rich   URL  Server  Based   HTML5  for  fully  op5mized  apps     Hybrid   Symbian   Web  OS   J2ME   §  Create  seamless  experience  for  end  users   Single  Page  Architecture     KonyOne  Studio   KonyOne  Server   Kony  Sync  Server   Kony  MAM  COMPONENTS           §  Form  Designer   §  Event  Editor   Device  Detec5on   §  Device  Detec5on   §  Alert  Services   §  Full  Offline   §  Console   §  Script  Editor   §  Service  Defini5on   §  Usage  Analy5cs   §  Device  Database   Usage  &   &  Analy5cs   Capability   §  Enterprise   §  Publish  /  Deploy   §  Data  Mapper   Flow  Controller   §  Flow  Controller   §  Mobile  Web  Hos5ng   §  Audit  Metrics   App  Store   Cross  Channel  API   Channel  Specific  ProperOes   Foreign  FuncOon  Interface   Connectors  FOUNDATION           §  UI  /  UX   §  UI  /  UX  /  Widgets   §  New  Device  API   §  Services   §  Device  Features   §  OS  Features   §  Non  –  UI   §  Data  Conn   §  U5lity   §  Third  Party  Workflow   §  ERP  /  CRM   Copyright  ©  2012  Kony  Solu5ons,  Inc.    CONFIDENTIAL   26   26  
  27. 27. QUESTIONS? More information on www.kony.com/resources www.kony.com Twitter: @konyCopyright  ©  22012 Kony olu5ons,  Inc.    CONFIDENTIAL   Copyright © 010  Kony  S Solutions, Inc. CONFIDENTIAL 27 27

×