3 ms·
A plan is not a decision. Creating a plan is not tantamount to deciding too early, it's just a good idea. Committing to the plan (especially a long range one)
by Jtsummers 6y ago
A plan is not a decision. Creating a plan is not tantamount to deciding too early, it's just a good idea.
Committing to the plan (especially a long range one) with no intent to deviate is just stupid, and is the critical flaw of Waterfall.
Agile is about responsiveness. In order to be responsive you need tight feedback loops (a reason the idea of sprints and scrum are ok). But are you responding if you don't have a plan? You aren't responding, you're reacting. Make the plan, but don't make a commitment too far out (commitments are kinds of decisions). Respond to changing circumstances and don't let yourself get caught in an action-reaction loop, because you can't react fast enough. At some point you have to think and respond.
Also, "decide as late as possible" is better read as "decide at the last responsible moment". If I know that I can get someone hired in two weeks, I can, in the first phrasing, wait until 2 weeks before someone retires to start that process. But it's not responsible. The last responsible moment is probably 2-4 months (at least) before the retirement so people can get trained up and moved around.