Sprint 10 :: How To Define Your Minimum Viable Product (MVP)
In our product life, we've all had to define a MVP.
Sometimes it's easier, sometimes it's harder, but what are the tips and tricks we can use when defining what is good enough to be an MVP?
First of all, it's important to clarify what an MVP involves - enough or satisfactory features for first users, with room for feedback to make future developments and improvements.
Before going into great detail, it is important to think big and idealize the whole scenario. Let's think about the whole solution to satisfy the users' needs, and from there, define what are the first priorities.
Let's not think about all the cool features and all the easter eggs that a product could have, let's first think about filling in what's missing... and then we'll make the difference with the details. How can we reach this? One of the models that we used the most until today was the MOSCOW model.
What is MoSCoW Prioritization?
Taking into account the illustration above it is easy to understand the differences between the various classifications, but let's explore a little more!
Must-haves:
These features are completely mandatory for the app or website to be released. Without this you cannot provide value to your customers.
Should-haves:
They are very important and precious details, but they are not the core of the app or the website. Do asap after the must-haves.
Could-haves:
Small or no impact on mvp. Almost always considered as extras and not always possible to measure how much it would improve the user experience.
Will not have:
Features that don't add anything and that shouldn't be part of a mvp, and they will hardly ever be considered as a good thing.
We hope this article helps you make your next decisions!
And you? What prioritization model do you use?
The Product Land ⛰️
Wanna know more? Stay tuned and subscribe for the next sprints! ☟
And also.. get in touch with us if you want to! 🌐