6 ms·
> Depending on your domain, 1 month is not enough to even understand the problem. I ran across this too in brief skimming (There's a lot there) but I assumed i
by gertlex 6y ago
> Depending on your domain, 1 month is not enough to even understand the problem.
I ran across this too in brief skimming (There's a lot there) but I assumed it was talking about building the MVP after doing the learning needed (in as much as you ever fully understand most domains) and designing of the MVP system.
- hcarvalhoalves 6y agoIf you follow Lean (where "Minimum Viable Product" originates from), there's no hard split between design/implementation phases, since the whole concept of MVP is avoiding waste in building something nobody wants. The keyword is "avoiding waste", not "build something in 1 month". You can still waste 1mo work pretending to be fast and shipping crap, that's not the point. The time a Minimum Viable Product will take is still completely determined by the requirements (definition of "viable", budget, experience, regulations, etc).