|
|
|
|
|
|
by Cafey
3482 days ago
|
|
|
>If the MVP takes longer than 3 month to build, you are barking up the wrong tree. It doesn't necessarily mean the product isn't fit or you lack skills. It may just mean that you need to split the product into smaller releases/sprints. Say your idea can ultimately lead to a really big software. You should sit down and spend some time planning which features are required and which ones can be released at a later time. Doing this will help take some of the pressure off if the product is not "perfect" or doesn't do everything you had planned for it. |
|
|
What I mean is to be wary of minimum number of features that you need to sell. Obviously if you were building a database to rival MySQL or OrientDB, the bar is that much higher.
Likewise, I think that if the MVP takes longer than 3 month for OP, it's wise to say that more resources are going to be required for that niche which OP may not have.
An MVP will signal whether the pain your customers is experiencing is urgent enough. If they start complaining why X doesn't work when Y has it then you've essentially created a vitamin solution, nice to have but nothing close to solving real pain points.