Building Debt Free MVP


Published on

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.

1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Building Debt Free MVP

  1. 1. SERGEY SUNDUKOVSKIY PH.D.Building Debt Free MVP1
  2. 2. Introduction2
  3. 3. Background3
  4. 4. AgendaDefining an MVPDebt AvoidanceTechnology SelectionInfrastructure SelectionProcess SelectionOrganizational Tool BeltAlpha  Beta Process4
  5. 5. Defining MVP5
  6. 6. Defining MVP6Eric Ries defines MVP as “…that version of a new productwhich allows a team to collect the maximum amount ofvalidated learning about customers with the least effort.”MinimalProduct nobodywants to useViableProduct builtby companiesthat have nofinancial limitationsMVP
  7. 7. Defining MVP7MarketFeaturesUsabilityMVPMVP is a product with aminimal set of features thatintended customer will buyand continuously use
  8. 8. Defining an MVPMVP vs. Prototype8
  9. 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 Money9
  10. 10. Adoption CurveWho is MVP for?10
  11. 11. MVP TargetingPrototype Targets InnovatorsMVP Targets Early AdoptersEarly Adopter Groups Educators Influencers Opinion Makers Social Connectors11
  12. 12. MVP Core FunctionalityIdeal MVP12
  13. 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 Pretty13
  14. 14. MVP FeaturesLess Is Truly More14
  15. 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 Intent15
  16. 16. Irreducible ComplexitySimplest Mousetrap16
  17. 17. Path To IntentStraightforward Path To Intent17
  18. 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 Faster18
  19. 19. Debt (Leverageable)19
  20. 20. Product DebtDocument Your Intent20
  21. 21. Intent Documentation ElementsIntent Documentation Assumptions Epics User Stories System Use Cases Business Rules Actors21
  22. 22. Product Debt (User Stories)As Who I Want This and Why22
  23. 23. Product Debt (User Stories)Watch Out For Myopic View23
  24. 24. Technical DebtThings Slow Down24
  25. 25. Support to Innovation RatioYou Are in the Support Business25Support(15%)Innovation(85%)Support(50%)Innovation(50%)Support(85%)Innovation(15%)Year 1Year 2Year 3
  26. 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 Recipes26
  27. 27. Architectural Blueprint27Typical Layered Architecture
  28. 28. Decision StackReverse Funnel28
  29. 29. Frameworks29
  30. 30. Language SelectionProgramming Language Is Irrelevant. It Only Matters inTerms of Resource and Starter Product Availability30
  31. 31. Infrastructures DebtAvoiding Infrastructure Debt31
  32. 32. IaaS + PaaSUse As Much of the Stack as You Can32
  33. 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 Control33
  34. 34. PaaS34
  35. 35. IaaS35
  36. 36. Process DebtDo Not Make It Complicated36
  37. 37. Process Complication Do Not Make It Complicated Complicated = Bad Complicated = Unsustainable Complicated = Not Followed Complicated = Edge Case Centric Complicated ! = Useful Complicated = Unintended Consequences37
  38. 38. Planned vs. Agile38VS
  39. 39. Planned vs. Agile Planned Process Exhaustive Planning (plan until you are exhausted) Prescriptive Document CentricAgile Process Iterative Planning Non-prescriptive Practice Centric39
  40. 40. Agile Umbrella40
  41. 41. Organizational Tool Belt41
  42. 42. Organizational Tool BeltOne Ring To Rule Them All42
  43. 43. Atlassian Suite43
  44. 44. Best of Breed44
  45. 45. Organizational Tool Belt45
  46. 46. MVP Testing46
  47. 47. Alpha (Are You Interested)Happy Path47
  48. 48. Alpha Testing What Do We Want to Know? Can You Complete a Happy Paths? Are You Confused? Are You Excited? Are You Bored?48
  49. 49. Private Beta (What Will You Do)We Are Watching You49
  50. 50. Private Beta We Are Watching You Hover Areas Attention Areas Click Areas Used FeaturedWe Are Measuring You Visit Duration Hover Time Return Frequency50
  51. 51. Public Beta (Charge Them Phase)Free Trial What Is It For?51
  52. 52. Public Beta What Kind of Customer Are You Going To Be? Active Passive Hibernating Advanced Intermediate Novice52