NVISIA shares key insight for building enterprise mobile applications by connecting business units with IT, using the 10x Leadership Disciplines as defined in the book Good to Great.

1. Technology Executives Club
Meeting the business's demand for Mobile Applications
May 9th, 2013
everything connects…

2. Partnering with the Business
Trend: Becoming a More Agile Enterprise
2 everything connects…
Develop a business-oriented approach to
supporting the business. Need an
approach to manage an overall can-do
attitude that supports the maximizing
business results
Develop an environment and a set of
blueprints to support agile development
practices while focusing on consistency.
30-90 day
delivery
cycles
Support for
many
devices and
device
specific
functionality
Competitive
Pressure
Very little
time to plan
and planning
is difficult
with the
amount of
change
happening
Growing list
of products
and
frameworks
to support
mobile
development
Growing list
of devices
Agile
Mobile
Environment
Business Demands Technology Environment

3. Partnering with the Business
“10x Leadership” Principles in Mobile
What and why 10x leadership…?
• Business-oriented approach to building a
relationship with the business
• Lessons learned on how 7 out of
20,400 companies beat their industry
index by at least 10 times.
• We see successful mobile adoption
3 everything connects…
trends aligning with the 3 key
behaviors of 10x leaders
Present trends for mobile in:
• Fanatic Discipline
• Empirical Creativity
• Productive Paranoia
Fanatic
Discipline
Productive
Paranoia
Level 5
Ambition
Empirical
Creativity
Great by Choice
Jim Collins and Morten T. Hansen

4. Partnering with the Business
“10x Leadership” Fanatic Discipline
Fanatic Discipline
• “The 20 mile march”, Amundsen vs. Scott, SWA vs. PSWA
Fanatic Discipline for Mobile: Committing to regular, frequent
releases
• Example: No matter what, we are releasing significant
4 everything connects…
enhancements every 45 days.
• Establish a tempo and get really good at keeping the tempo
• This starts with embedded Business Analysts, with OOM estimating
skills to collaborate on priorities for each release.
• Takes the pressure off of any single release plan – If your feature
misses the cut-off for next release, it doesn’t mean that your users
are waiting another year for their feature.

5. Partnering with the Business
“10x Leadership” Empirical Creativity
Aim
5 everything connects…
Empirical Creativity
– “Bullets, then Cannon Balls”
Empirical Creativity for Mobile:
Iterative, Incremental Development
– Get empirical data based on small, targeted
applications/features before making any
large investments
– Agree on content, goals and metrics for
each iteration
– Agree on the success criteria and exactly
how it will it be measured
– Don’t move the user’s cheese too far in any
one release
– The key is in developing the release plan
with the business
Calibrate
with
Bullets
Fire
Measure
Adjust

6. Partnering with the Business
“10x Leadership” Empirical Creativity (2)
Empirical Creativity in Planning the Mobile App
• Provide useful data to the business, before building anything
– Example: Google Analytics – Mobile Visitor Analysis
6 everything connects…

7. Partnering with the Business
“10x Leadership” Empirical Creativity (3)
Planning the Release Cycle with the Business
• Establishing priorities and high-level estimating is key
• Cross-train Business Analysts – Understanding the technical and
business environment
– Quickly identify low hanging fruit – Move some easy win’s up the release list
– Agree on risk plan, retire show stoppers as early as possible
• Be ready to reinvent business process/requirements management for
Mobile applications – improve business outcomes
– Finding process that are impacted by greater context (additional real-time
info that helps for make a better decision) to improve outcome
– Using context to shorten process time for users
– Embed business analysts with real users to understand and exploit context
7 everything connects…
rich opportunities

8. Partnering with the Business
“10x Leadership” Productive Paranoia
8 everything connects…
Productive Paranoia
– “Highly attuned to threats and changes especially when things
are going well. Fear and worry is channeled into preparation,
contingency plans, buffers and margins of safety”
Productive Paranoia for Mobile:
– Lost or stolen devices – Data…?
– Business process interrupted when signal drops
– Slow adoption because of bad app store reviews
– What if we are really successful! …and our mobile solutions do
not scale up:
• Performance: ability to add lots of users
• Functional: Ability to add feature that require integration across multiple
systems
– Vendor goes out of business or key resources are unavailable

9. Technical Considerations
Technology Environment
Technology Environment for Mobile
Development is changing rapidly
• Similar to past patterns – tools looking to
9 everything connects…
simplify development
• Similar amount of activity to web-based
development
• Those based on standards have a better
chance of surviving
• But.. The standards are still being developed
This amount of change makes planning more
difficult
• Temptation of the silver bullet
• Temptation to get “something out there”
• BTW – may be the correct solution
• Temptation to delay decisions – leads to business
frustration and inconsistent solutions
MEAPs
HTML
5
Native

10. Technical Considerations
Leverage Blueprints and Standards
Typical
lifetime
3-6
months
2-5
years
10 everything connects…
Roadmap - Decide on what mobile
technologies you can and will support
Blueprints - Focus on creating a set of
standard frameworks and integration
patterns for each supported environment
• Native iOS
• Native Android
• Mobile Web/HTML5
• Responsive Web Design
• Work on isolating the frameworks chosen to
lessen dependence
Mobile
Apps
Business
Services
Core
Systems
10-20
years
Focus - Create decision criteria that helps determine which implementation option
is best for the required functionality
• Work with the business on this – make them part of this decision process
Integration - Focus on reusing business services whenever possible

11. Technical Considerations
Mobile Development Environment
Create a mobile application
development environment
• Built using the Blueprints established earlier
• Templates/Sample code for patterns
• Focus on architecture to isolate
Mobile Development Environment
Developer
Environment
Configuration
Management
Release
Management
Testing Environments
Load and
Performance Testing
11 everything connects…
frameworks and technologies as
appropriate
• Development Environment
• Version Control
• Continuous Build Environment
• Mobile Specific Test Environment and Plan
• Testing (System, UAT, Performance, etc.)
environments
Spend time on defining and optimizing your development and release
process
• How can you support multiple development streams simultaneously?
• How can we shorten the deployment time?
• How can we shorten our testing time without sacrificing quality or coverage?
….

12. Where to Start
Setting Goals for Mobile Best Practices
10x Behavior Driver Strategy Goal
12 everything connects…
Fanatic Discipline Steady tempo to demonstrate
steady progress and allow for
frequent empirical measurement
Frequent Releases 45 day internal release cycle
Empirical Creativity Need to focus on core business
requirements first
Gain agreement with the
stakeholders regarding priorities -
not everything is high priority
A consistent prioritizations
methodology is defined
Empirical Creativity Guide the business to the highest
value features with the lowest
associated effort
Cross train BA's on technologies
and existing solutions
BA's understand core systems and
main data areas
Empirical Creativity Need to collect empirical data
from user behavior/technologies
to make better decisions
Use analytics tools to collect data
for current and future systems
Set up and capture analytics for
existing mobile or web apps
Productive Paranoia Bad user experience slows
adoption
Rigorous testing for all platforms Test plan for mobile
Productive Paranoia An uncertain technology
landscape makes changes in
technology a near certainty
Consistent Standards and
Blueprints to make changes and
upgrades easier
Define Blueprints for each area

13. Where Our Trend Data Came from
13 everything connects…
NVISIA Introduction
Experience with enterprise customers where:
• Increasing business agility is critical to their business
• Building a sustainable competitive advantage through software
innovation is part of their business strategy
• New applications require high degree of integration or interoperability
across multiple systems
Recent Examples…

14. Questions and Contact Information
14 everything connects…
Thank You
Shaun Lovick
• shaunl@nvisia.com
• Mobile: 312.493.4180
Mark Panthofer
• mpanthofer@nvisia.com
• Mobile: 262.995.4173