3 ms·
It started with scratching my own itch, and I've done a lot of customer validation since then (not as much as I'd like, but enough). So in this case, the MVP is
by beat 13y ago
It started with scratching my own itch, and I've done a lot of customer validation since then (not as much as I'd like, but enough). So in this case, the MVP is about limiting scope, not doing things that don't scale. Doing it manually is not "perfectly fine", because the problem is that it's already being done manually, and needs to be automated. "Manual" and "viable" are incompatible in my case.
Which gets to the author's point.
- rmoriz 13y agoThere are many things that can be automated and we developers believe this is some kind of value, however a MVP is about customer validation: If you have not validated your product, it's harmful to automate it. If you have customers and they pay for automation, you don't have a MVP anymore. You're already playing in the next level.