|
It's an excuse to do inadequate planning. "Oh yeah, we have to remain agile to our customer's needs. Let's not spend focused effort up front to get a full accounting of the exact requirements and instead just sit back and accept doing a half-assed job there so that when inevitably the customer comes up with more stuff we missed the first time (because we didn't ask/scope properly) we can pretend like that's part of our strategy rather than us being lovely at planning things." See also: MVP - make something really lovely, really fast and sell it on the promise that "don't worry, it'll get better eventually!" Nobody wants to pay for the improvements, partially because the lovely thing you made wasn't ever really properly designed to handle them. lovely thing becomes the thing everyone now has to use to do their work because of the sunk cost fallacy of having paid money to implement it and the false promises of 'and it has so much potential'. Until senior management changes, they go, "what's this lovely thing and why are we using it? Throw it out! You know what, we should get a better tool. Get someone to make me an MVP for that" and the cycle continues. Maybe that's why those Agile diagrams are all circles - they all end up back where they started in the end.
|
#
¿
Nov 20, 2019 23:56
|
|
|
|
| # ¿ May 15, 2024 10:34 |
|