Thanks for sharing your feedback and question, Belirle. It seems to me that the issue in your scenario is empowerment: Who is empowered to decide the features a product release should contain? Is it the product owner, the team, a senior stakeholder, or someone else? I recommend that the person in charge of the product has the final say on the features offered, as I discuss in more detail in the article Understanding Empowerment in Product Management. Hope this helps!

Hi Felix,

Thank you for sharing your feedback. Please take a look at my article “Tips for Rewriting a Digital Product“, which should answer your questions.

Roman

Thank you for this post. How would you approach scoping MVP, MMP and full product functionality if you had to replace an existing, very successful product, that has to be re-implemented on a new technology basis. Would you rather spend more time implementing more features to replace the old with the new as seamless as possible with regards to functionality or would you try to change to the new version as quick as possible? Obviously, that is also a strategic decision, but nevertheless … what are your thoughts?

Thank you!
Felix

Hi Geert,

What matters most, in my mind, is that you have a shared understanding of what the term minimum viable product means in your organisation. Additionally, aim to launch a minimal, good-enough product and adapt it to the market response, as suggested in the post scriptum of the article.

Hope this helps!

What are your thoughts on the idea that some people have started using MVP and MMP interchangeably; do you believe it is correct to do so? In my opinion it is a confusion of the concepts perhaps caused by a lack of understanding the distinction between them, and I am curious about how others view the matter.

Many thanks.

Thanks for your comment and feedback Geert!

This piece is a very good explanation of the two different concepts MVP and MMP, and I am especially noticing your P.S. where you mention that the term MVP has started to change, and you refer to an article where MVP is defined as “The smallest thing you can build that delivers customer value”, which to me seems to be the very definition of MMP.

Keeping in mind that the focus in MVP is learning, and in MMP the focus is on earning, the MVP provides value to a business by learning from early users of a product/system, and the MMP provides value to a business that will use the learning from MVP to build an MMP whereby the focus shifts to earning.

Could it just be that some have confused the two concepts and, wrongly, use them interchangeably, which is a mistake in my view? From the Agile Alliance we know that “the primary benefit of an MVP is to gain an understanding of your customers’ interest in a product without fully developing the product”, which to me is the MMP, meaning that they are in fact two different concepts. What are your thoughts on this?

Again, many thanks for a great article about the topic, I have bookmarked your article for later reference 🙂

Thanks for your feedback and suggestion John. I write more about MVPs and the topics you mention in my book Strategize. Hope this helps.