*Spoiler Alert: [This is a long post, you might want to get yourself a cup of hot coffee! It walks you through the idea of what happens next after MVP development, what is MMP and why it comes after agile minimum viable product and how to bridge the gap between MMP and MVP with links to resources. Now, you see why you will need that hot drink. ;)]
As I was saying in the last write up, the idea of building an MVP is tricky. All you need is a user-centric approach and create an MVP that stands out. It should be desirable and accepted by the mass. After you have the agile minimum viable product developed and validated, you just need to iterate on the feedback and develop rapidly.
Yet I meet a number of people who feel lost after the MVP is built. They don’t know what is next after MVP.
Why so? What makes them get confused?
MVP is a process and not a product — Eric Ries
Yevgeniy (Jim) Brikman was right in explaining this hullabaloo. He spotted the wrong in the whole picture and explains why Eric Ries calls “MVP is a process and not a product.” Rather it is just a proof of concept. If the MVP works well, a startup plans on building the mature product.
That all looks very perfect.
