§ 108
The Last Responsible Moment
Commit too early and a guess hardens into the design; wait too long and an option quietly expires, so the decision gets made by default without anyone making it.
Keep in mind
Know when each decision expires, and decide before it does
What to do
For each open design decision, write down the event that would remove an alternative (a contract date, a release that freezes an interface, another team starting to build on it) and put its date on the calendar. Decide before that date, not on it. Do not use this to postpone decisions that unblock other work or that shape everything after them, such as layering.
Why it happens
At the start of a project the team knows least, and an early commitment narrows the field of view before the facts arrive. Holding a decision open lets learning catch up. But every open decision has a deadline that nobody announces: the Poppendiecks define the last responsible moment as "the moment at which failing to make a decision eliminates an important alternative." A contract renews, an API ships and gets callers, another team builds on an assumption, and the alternative is gone. "If commitments are delayed beyond the last responsible moment, then decisions are made by default, which is generally not a good approach to making decisions." They add that some decisions, such as usability design, layering and component packaging, are best made early, and that "A bias toward late commitment must not degenerate into a bias toward no commitment."
When it stops applying
Most Responsible Moment: Wirfs-Brock finds she cannot tell when the last responsible moment is, and that aiming for it lulls her into thinking there will always be time to change her mind; she prefers to decide as soon as a decision has a positive impact, which often comes earlier.
Source
Mary & Tom Poppendieck, Lean Software Development: An Agile Toolkit (Addison-Wesley, 2003), ch. 3, "Tool 8: The Last Responsible Moment", pp. 57–59 — the definition, "decisions are made by default" and the warning against a bias toward no commitment; they credit the term to the Lean Construction Institute. Rebecca Wirfs-Brock, "Agile Architecture Myths #2 Architecture Decisions Should Be Made At the Last Responsible Moment" (2011) — the "most responsible moment".
Read the sourceCite this
Hammurabi, § 108, “The Last Responsible Moment.” https://kanywst.github.io/hammurabi/laws/last-responsible-moment/
BibTeX
@misc{hammurabi-last-responsible-moment,
title = {The Last Responsible Moment},
author = {{Hammurabi contributors}},
note = {Hammurabi, § 108},
url = {https://kanywst.github.io/hammurabi/laws/last-responsible-moment/}
}Read in a column
- Deciding what to build Next in the column: Pre-Mortem
Related laws
- 01Type 1 vs Type 2 DecisionsTeams spend the caution meant for irreversible decisions on ones they could easily undo.
- 58YAGNICode built for imagined future needs costs time now and rarely fits the need that arrives.
- 107Cost of DelayWork gets ordered by size, by gut feel or by whoever asks loudest, while what each item loses every week it waits goes uncounted, so the most valuable work often waits behind the merely visible.
- 76Disagree and CommitWaiting for everyone to agree is often slower than committing and correcting course if the call turns out wrong.
