3 ms·
Two things: 1) You can end at the first iteration and call it a day. The only reason nobody does that is because they don't benefit from an unhappy customer 2
by atoav 3y ago
Two things:
1) You can end at the first iteration and call it a day. The only reason nobody does that is because they don't benefit from an unhappy customer
2) If you have experience, nothing stops you from putting some iterations into the waterfall. As you said the need for feedback rounds should be no surprise.
Traditionally the downside to waterfall was that the distance between those iterations was too big. But smaller iterations and partly prototypes is nothing that wouldn't be allowed in waterfall if you'd like to do it. And if you find a PM that doesn't do the reasonable thing "because the methodology won't allow it" they are probably a bad PM.
- xwolfi 3y agoFor me the goal of Agile, especially in giant 100+ yo organization, is to tell people that it's less important to fit the plan than to fit the need of the external stakeholder. Who cares if 6 months ago some important managing director signed off on a useless feature nobody wants anymore: kill it now and move on, we're agile. This is literally the only way I've seen used agile in big orgs: in words only, and it's liberating: we stop spinning endlessly between useless features as the clients move on faster than us, now we can actually skip a beat and go faster, and screw the paper pushers bemoaning that "everything changes". Because yes, everything changes.