“We Scrum and we plan to deliver our MVP next year” cover image
Product Ownership

“We Scrum and we plan to deliver our MVP next year”

Creating an MVP through iterative delivery and constant customer feedback.

Profile image of Willem-jan Ageling
Willem-jan Ageling
Jul 14, 2019 • 4 min read
4.24 (21)
Minimum Viable Product (MVP)
Customer Focus
Transparency
Adaptation
Empiricism
Show more

Summary

Willem-Jan Ageling writes about Minimum Viable Product (MVP) and the importance of Scrum when deploying an MVP, suggesting that Scrum is all about empiricism and helping stakeholders make potential future customers part of the product's journey. He also acknowledges that MVPs help reduce the risks of burning out cash on a product that might not coalesce with the customers as they enable early users to interact and provide feedback for the product's development. Check the article to gain more insight into what is an MVP, its impact on future potential customer development, and the role of Scrum in MVPs.

Takeaways

  • A minimum viable product (MVP) is a product with just enough features to satisfy early customers and provide feedback for future product development.
  • MVPs allow early users to interact with the product, provide excellent feedback, and pave the way to probably become great advocates of the product.
  • Scrum brings transparency, inspection, and adaptation when delivering an MVP thus mitigating the chances of developing the wrong product.
  • When building an MVP, don’t forget to inspect the Increments in order to adapt the Sprint Backlog. The most transparent way to inspect the Increment is by giving (a set of) future users the opportunity to work with very early versions.

Suggested Resources