What's my MVP?

One of the customer I recently interacted, wanted me to do BA coaching(as they called) for the teams they wanted to transform towards Agile :)

What's my MVP?

Before diving into user stories, I just wanted to ensure they understand their product vision and product goal and hence asked about MVP. Minimum Viable Product(MVP) is one of the important tool of the iterative process or having successful agile journey. But challenge I realized was, teams weren't aware of what it is or how to define it.Hence, I am making an effort in this post to help you getting started with MVP. As per Wiki, In product development, the minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future development. Some experts suggest that in B2B an MVP also means sale-able: "it’s not an MVP until you sell it. Viable means you can sell it". While defining MVP, ask clients to identify what is most important: Time to market? budget? Or the features that act as USP for you?For example, if a client says that time to market is the priority, it is likely that we might deliver product, with certain known bugs so as we finish the product quickly and get it out the door before their competitor does. If they tell us they have a budget constraint, then might have to drop certain features, so as we can deliver with in short span of time. In one of the cases,we build a minimum viable product (MVP) as a proof of concept, spending a lot of time arguing about which features to include or exclude from the MVP. Finally, if the MVP works well, we plan on building the full, mature, stable product. But wait, MVP is not just a product with half the features, or a way to get the product out the door a little earlier. In fact, it doesn’t have to be a working product, or its just made once. It is also a way to test assumptions. to get answer to how architect would function and sustain. It ensures trial and error and helps team fail fast before they deep dive. This obviously required constant feedback and continuous interaction between business and team. So in my opinion to have successful MVP, - Prioritize the requirements - Identify highest risk around highest priority requirement - How can you make this assumption a reality with experiment? Answer to these questions is something that only helps you understand system in depth but also get answer to many hidden facts. Again as I mentioned earlier, revisit these questions in cadence to make sure you create sustainable product! Before I leave - do remember to TEST your MVP!


Leave a Comment

Your email address will not be published. Required fields are marked*

Sign Up for Newsletter

We use cookies to ensure you get better browsing experience on our website.

I Agree    Close