4 ms·
It doesn't even need to "not work." You can ship a V1/prototype/MVP product that does work with a small, focused team. But extending that product to support all
by jacobr1 4y ago
It doesn't even need to "not work." You can ship a V1/prototype/MVP product that does work with a small, focused team. But extending that product to support all the additional use cases, resolve feedback, address tech-debt/scale/performance, etc ... requires investment ... more investment probably than the initial version. But the version version is "done" - why invest more?
- VyseofArcadia 4y agoThat is a perfectly reasonable and understandable situation that I am not talking about. If Team B came to us and said, "here's what it does right now, we were only able to ship the MVP before we needed to prioritize other work", that's fine. That's wonderful. That is the kind of open and honest communication about platform capabilities that is necessary to do quality work. What I am talking about is when Team B says, "it slices! It dices! It removes tough stains, washes and dries your cloths, hell, it'll fold them!" Then when you start working with their amazing miracle product you find that it merely slices, well, no, actually, it really needs more of a sawing motion because they initially misunderstood the requirements and built it serrated and didn't have time to go back and fix it.