MVP Definition
MVP Tests (2, page 89)
- MVP tests are everything that tests the hypothesis
- MVP is reserved for the actual product
MVP Prerequisites
Steps to take before building an MVP (2, page 87)
- Formed hypotheses about your target customers
- Formed hypotheses about their underserved needs
- Articulated the value proposition you plan to pursue so that your product is better and different
- Identified the top feature ideas you believe will address those needs and broken them down into smaller chunks
- Prioritised those feature chunks based on ROI
- Selected a set of those feature chunks for your MVP candidate, which you hypothesize customers will find valuable
MVP Guidance
MVP Questions (1, page 77)
- Most important question is ‘What’s the most important thing we need to learn next about this hypothesis?’
- Next question is ‘what is the least amount of work we can do to learn that?’
MVP Functionality (2, page 89)
An MVP should address all of the needs from Olsen’s hierarchy – it should not be just functional – it should be usable and delight the user
References
- Lean UX by Jeff Gothelf
- Lean Product Playbook by Dan Olsen
Explore more
 Refinement |  User Stories |  User Testing |
scrumlog.org 
One thought on “Minimum Viable Product (MVP)”