Upload
sergey-sundukovskiy
View
677
Download
2
Tags:
Embed Size (px)
DESCRIPTION
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.
Citation preview
SERGEY SUNDUKOVSKIY PH.D.
Building Debt Free MVP1
Introduction2
Background3
Agenda
Defining an MVPDebt AvoidanceTechnology SelectionInfrastructure SelectionProcess SelectionOrganizational Tool BeltAlpha Beta Process
4
Defining MVP5
Defining MVP6
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.”
MinimalProduct nobody
wants to use
ViableProduct built
by companiesthat have no
financial limitations
MVP
Defining MVP7
Market
Features
Usability
MVP
MVP is a product with a minimal set of features that intended customer will buy
and continuously use
Defining an MVP
MVP vs. Prototype
8
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
Adoption Curve
Who is MVP for?
10
MVP Targeting
Prototype Targets InnovatorsMVP Targets Early AdoptersEarly Adopter Groups
Educators Influencers Opinion Makers Social Connectors
11
MVP Core Functionality
Ideal MVP
12
Ideal MVP
Mini-Me is an Ideal MVPCore Functionality
Identical “DNA” Same Major Features Same Major Functionality Same Usability Not Up To Scale Not As Pretty
13
MVP Features
Less Is Truly More
14
MVP Attributes
Intelligent Design ConceptsIrreducible 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
Irreducible Complexity
Simplest Mousetrap
16
Path To Intent
Straightforward Path To Intent
17
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
Debt (Leverageable)19
Product Debt
Document Your Intent
20
Intent Documentation Elements
Intent Documentation Assumptions Epics User Stories System Use Cases Business Rules Actors
21
Product Debt (User Stories)
As Who I Want This and Why
22
Product Debt (User Stories)
Watch Out For Myopic View
23
Technical Debt
Things Slow Down
24
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
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
Architectural Blueprint27
Typical Layered Architecture
Decision Stack
Reverse Funnel
28
Frameworks29
Language Selection
Programming Language Is Irrelevant. It Only Matters in Terms of Resource and Starter Product Availability
30
Infrastructures Debt
Avoiding Infrastructure Debt
31
IaaS + PaaS
Use As Much of the Stack as You Can
32
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
PaaS 34
IaaS 35
Process Debt
Do Not Make It Complicated
36
Process Complication
Do Not Make It Complicated Complicated = Bad Complicated = Unsustainable Complicated = Not Followed Complicated = Edge Case Centric Complicated ! = Useful Complicated = Unintended Consequences
37
Planned vs. Agile38
VS
Planned vs. Agile
Planned Process Exhaustive Planning (plan until you are exhausted) Prescriptive Document Centric
Agile Process Iterative Planning Non-prescriptive Practice Centric
39
Agile Umbrella40
Organizational Tool Belt41
Organizational Tool Belt
One Ring To Rule Them All
42
Atlassian Suite43
Best of Breed44
Organizational Tool Belt
45
MVP Testing46
Alpha (Are You Interested)
Happy Path
47
Alpha Testing
What Do We Want to Know? Can You Complete a Happy Paths? Are You Confused? Are You Excited? Are You Bored?
48
Private Beta (What Will You Do)
We Are Watching You
49
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
Public Beta (Charge Them Phase)
Free Trial What Is It For?
51
Public Beta
What Kind of Customer Are You Going To Be? Active Passive Hibernating Advanced Intermediate Novice
52