This presentation is a continuation of a "What To Do Once You Have an Idea". It explores a process of defining and building an MVP. It emphasizes building an MVP in a sustainable way while avoiding taking on unnecessary Product, Technical, Infrastructure and Process Debt. It also looks at the options of utilizing tools for effective Debt management.
6. Defining MVP
6
Eric Ries defines MVP as “…that version of a new product
which allows a team to collect the maximum amount of
validated learning about customers with the least effort.”
Minimal
Product nobody
wants to use
Viable
Product built
by companies
that have no
financial limitations
MVP
9. MVP vs. Prototype
MVP
Test Product Viability
Test Assumptions
Test the Market
Test Product Usability
Get User Feedback
Prototype
Demonstrate the Concept
Convince Others That You Are Serious
Get Seed Money
9
13. Ideal MVP
Mini-Me is an Ideal MVP
Core Functionality
Identical “DNA”
Same Major Features
Same Major Functionality
Same Usability
Not Up To Scale
Not As Pretty
13
15. MVP Attributes
Intelligent Design Concepts
Irreducible Complexity
Can’t Take Anything Away
Can’t Be Simpler
Most Efficient For What It Does
Most Efficient Wins
Most Efficient Survives
Path to Intent
Most Straightforward Path to Intent
15
18. Debt
Everything you want to do “Later” is DEBT
Let’s Document Later
Let’s Test Later
Let’s Architect Later
Let’s Refactor Later
Debt Misconceptions
All Debt is Bad
No Debt is Great
Taking on Debt Gets You There Faster
18
25. Support to Innovation Ratio
You Are in the Support Business
25
Support
(15%)
Innovation
(85%)
Support
(50%)
Innovation
(50%)
Support
(85%)
Innovation
(15%)
Year 1
Year 2
Year 3
26. Technical Debt Elements
Technical Debt Elements
Lack of Architectural Blueprint
Lack of Unit Testing
Lack of Integration Testing
Lack of Code Reviews
Lack of Starting Platform
Lack of Starting Framework
Lack of Technical Design
Lack of Development Recipes
26
33. Infrastructure Debt Elements
Infrastructure Debt Elements
No Utilizing IaaS/Pass
Lack of Monitoring
Lack of Redundancy
Lack of Disaster Recovery
Lack of Environment Separation
Dev Ops Debt Elements
Lack of Deployment Framework
Lack of Continuous Integration
Lack of Effective Source Control
33
37. Process Complication
Do Not Make It Complicated
Complicated = Bad
Complicated = Unsustainable
Complicated = Not Followed
Complicated = Edge Case Centric
Complicated ! = Useful
Complicated = Unintended Consequences
37
39. Planned vs. Agile
Planned Process
Exhaustive Planning (plan until you are exhausted)
Prescriptive
Document Centric
Agile Process
Iterative Planning
Non-prescriptive
Practice Centric
39
50. Private Beta
We Are Watching You
Hover Areas
Attention Areas
Click Areas
Used Featured
We Are Measuring You
Visit Duration
Hover Time
Return Frequency
50