The document discusses the differences between minimum viable products (MVPs) and minimum marketable products (MMPs). It defines an MVP as the smallest version of a product that allows a team to collect validated learning about customers with minimum effort. An MMP is the smallest feature set that addresses the needs of early adopters and performs at least one customer job. The document provides examples of MVPs and MMPs and outlines strategies for using MVPs to validate hypotheses, reduce risks, and gather feedback before developing an MMP to launch and market the product.
8. MINIMUM VIABLE PRODUCT (MVP)
• “that version of a new product which allows
a team to collect the maximum amount of
validated learning about customers with the
least effort” – Eric Ries
26-Oct-2019I.Yamshanov, BAQ Conference
8
10. MINIMUM VIABLE PRODUCT (MVP)
• Input: Vision, OKR, Canvas (BMC, VPC, EMC)
• Hypotheses:
• Test them to know more about users and product for them
• Prioritize them and address most critical first
• Questions to consider:
• Is it a correct question that I want to answer?
• Can I rephrase the question to get the answer easier?
• Can I rephrase the question to answer more questions with less effort?
26-Oct-2019I.Yamshanov, BAQ Conference
10
12. MINIMUM VIABLE PRODUCT (MVP)
• Reduce risk
• Spend as little time and effort to create MVP as possible
• Proof of Concept as part of MVP to address technical risks
• Throwaway prototypes
• Simulate functionality
• For potential customers as demo, beta testers and
innovators
• Teambuilding practice
26-Oct-2019I.Yamshanov, BAQ Conference
12
14. MINIMUM MARKETABLE PRODUCT
(MMP)
• Do at least one customer job
• The smallest possible feature set that addresses the
needs of innovators and early adopters
• Consists of Minimum Marketable Features (MMF),
that provides maximal value (apply SPIDR, INVEST
for get it)
• Follow prioritized roadmap (Kano, WSJF)
26-Oct-2019I.Yamshanov, BAQ Conference
14
17. INVEST
• Independent – standalone PBI with no dependencies
• Negotiable – can be changed in anytime
• Valuable – having value for the stakeholders
• Estimable – the team is able to estimate
• Small – could be developed and tested in 1 sprint
• Testable – testing is possible based on AC and DoD
26-Oct-2019I.Yamshanov, BAQ Conference
17
20. CONCLUSIONS
• Make sure that client and project team understand
MVP in the same way (MVP ≠ MMP)
• Learn and reduce risk first
• Split functionality to maximize product value
• Make releases more frequently to quicker get
customers’ feedback
26-Oct-2019I.Yamshanov, BAQ Conference
20