4 ms·
Yes and that’s what almost everyone does. Learning loops with prototypes til you have a feasible product. But then you need a big development plan for how to sc
by rubidium 6y ago
Yes and that’s what almost everyone does. Learning loops with prototypes til you have a feasible product. But then you need a big development plan for how to scale it to a polished, sellable product. Because there’s a lot more to the product then the artifact.
- lmm 6y ago> But then you need a big development plan for how to scale it to a polished, sellable product. Because there’s a lot more to the product then the artifact. That's a total non sequitur. Agile is all about building the sellable product. But doing it iteratively works a lot better than doing it via a big development plan.
- rubidium 6y agoYou’re getting downvoted because you may have missed my point. To clarify for your sake, once you have hardware in the loop (eg mechanical engineers designing things, manufacturing scaling for production) and a large commercial organization who needs to be ready for a product launch, you need a waterfall type plan. Agile principles (customer focus, respond to change) can apply, and you can break up the work into 2 weeks, but you do need to look past the next 2-4 weeks and know where things are planned. Commitments matter in the $millions. Software-only SAAS has the luxury of avoiding that complexity.