4 ms·
MVP should always be about minimizing the number of features or things it does -- but never about delivering features that are broken or buggy. Everything you
by jrochkind1 13y ago
MVP should always be about minimizing the number of features or things it does -- but never about delivering features that are broken or buggy.
Everything you _do_ deliver needs to be polished and robust, or people are going to write you off.
It's really hard to pare down the feature set and figure out what features are really needed.
On the other hand, it's really easy to throw in a bunch of features, but have them all be half-broken crap with a poor UI.
The hard one is the one you actually need to do to be successful. You do need to pare down features to an MVP, because otherwise you're never going to finish, or are going to deliver crap. You need to pare down to the MVP, so that you have the resources to make every feature that remains high quality.
- jacobr1 13y ago> You do need to pare down features to an MVP, because otherwise you're never going to finish, or are going to deliver crap. Or deliver something beautiful to your team that no one actually wants, or will purchase