What breaks when iterative delivery is wrapped in a fixed scope, fixed date and fixed budget?
answer
- Every plan needs one variable
- Four levers, and one is never written down
- Feedback you may not act on is waste
- Rank the scope instead of closing it
- Name the variable or quality becomes it
basics
~20 sFixing scope, date and budget together removes the one variable iterative delivery needs. Iterations then report against a plan nobody may change, the quality bar becomes the release valve, and the programme pays a sequential plan's rigidity plus iteration overhead.
solid answer
~50 sIterative delivery earns its keep by **flexing scope against a fixed date and team**. Fix all three corners and there is nothing left to flex, so the flexing happens somewhere unmanaged — usually in quality, the one dimension nobody wrote down. Four things break in order. Feedback stops being actionable, because acting on it would change a scope that is contractually closed. Iterations degrade into progress reporting against a plan. The quality bar erodes silently as the date approaches. And the programme carries both costs: the rigidity of an early commitment plus the coordination overhead of short cycles. The renegotiation is to fix the **date and the budget**, and make **scope ranked rather than closed**: commit to an outcome and a minimum viable set, and let the ranked remainder absorb the variance. If the sponsor will not move, say plainly which corner is already flexing.
go deeper
Recall that iterative delivery needs one thing free to move, usually scope, and that fixing everything at once means the flexing happens somewhere nobody is watching.
Explain the four levers and be able to trace what happens step by step when scope, date and budget are all fixed — feedback becoming unusable and the quality bar quietly absorbing the pressure.
Show you can spot the failure mode from evidence, such as findings that are logged and never scheduled, and can propose a concrete re-plan cadence rather than complaining about the constraint.
Own the negotiation. Bring a specific proposal — ranked scope with a committed minimum, a written quality bar, a stated re-forecast cadence — and be able to say plainly, in writing, which corner is already flexing when the sponsor will not move.
## Why the shape is unstable A delivery plan has four levers: **scope, date, cost (which for software mostly means team size) and quality**. Any planning approach picks which ones are fixed and which absorb variance. A sequential plan fixes scope early and lets the date and cost move when it turns out to be wrong. Iterative delivery inverts that: the date and the team are fixed, and scope absorbs the variance, which is precisely what makes short feedback loops worth having — feedback is only valuable if you are permitted to act on it. The hybrid under discussion fixes scope, date **and** budget simultaneously and then asks a team to work in iterations. It has removed every declared variable while keeping the machinery that exists to consume one. Variance does not disappear because a governance document omitted it; it relocates to the only lever nobody wrote down, which is quality. That is why this shape has a reputation: it inherits the rigidity of an early commitment and the coordination overhead of short cycles, and gets the benefit of neither. ## What breaks, in order 1. **Feedback stops being actionable.** A user tries a slice and reveals a better answer. Acting on it means changing scope, and scope is closed, so the finding is logged and abandoned. The team keeps paying for the feedback loop and stops collecting the return. 2. **Iterations become reporting.** With nothing to decide, the iteration boundary degrades into a checkpoint that answers *are we on plan* rather than *what did we learn*. The ceremonies survive as status meetings, which is what people mean when they say the process is theatre. 3. **The quality bar erodes silently.** As the date closes, something must give. Checking is deferred, review is skipped, a temporary workaround becomes permanent. Nobody decides this; it is what the constraint set forces, and it is invisible until after handover. 4. **Escalation becomes personal.** Because no lever is available to the team, every problem arrives at the sponsor as bad news rather than as a choice between options. Trust degrades exactly when it is most needed. | Corner fixed | What it genuinely buys | What it costs when fixed with the others | |---|---|---| | Scope | A contract someone can sign | Feedback becomes unusable | | Date | External coordination, a market or seasonal window | Time pressure lands entirely on quality | | Budget / team size | Predictable cost, funding approval | No capacity relief when scope proves larger | | Quality (never declared) | — | Becomes the default variable by omission | ## What to renegotiate, in order - **Make scope ranked, not closed.** Commit to an outcome and a minimum set that must exist, then hold the remainder as a ranked list the sponsor reorders every iteration. The sponsor keeps control of *what*; the team gets a variable. This is usually acceptable because sponsors want the outcome, and the itemised scope was only ever a proxy for it. - **Fix date and budget deliberately, and say so.** These are the two that external parties actually plan around, and admitting that they are the fixed pair makes the tradeoff explicit rather than accidental. - **Declare the quality bar as a fixed constraint too.** Write down what must be true of anything called finished, so that eroding it becomes a visible decision requiring a signature rather than a quiet consequence of the calendar. - **Re-plan on evidence, on a stated cadence.** Agree in advance what happens when measured progress diverges from plan: which ranked items drop, who decides, and how fast. An escalation path agreed in month one is a process; the same conversation in the final month is a crisis. ## When the fixed triple is real anyway Sometimes a corner truly cannot move, and pretending otherwise is its own failure. A 4-person team building a lift-pass system for a ski resort faces a date set by the mountain: the season opens, 23 gate readers are already fabricated, and the installation window is 6 days. No amount of renegotiation moves the snow. The right response is not to fight the date, it is to refuse to fix scope alongside it. Define the minimum that must work on opening day — one pass type sold and validated at every gate — and rank everything else beneath it: seasonal pricing variants, family passes, the refund path for a closed lift. The date holds, the budget holds, the quality bar for the minimum holds, and the ranked tail absorbs every surprise the 11-week build produces. The principal-level point is that **you do not get to have no variable.** You only get to choose whether the variable is one you named and manage, or the unnamed one that shows up as defects after handover. Saying that out loud, early, with a concrete proposal attached, is the job.
- The sponsor refuses to rank scope and insists all three corners hold. What do you actually do?Make the fourth lever visible in writing. State which corner is already absorbing variance, describe what that looks like concretely — deferred checking, workarounds becoming permanent — and record the decision as the sponsor's, not a team failure. Then re-forecast on measured evidence at a stated cadence so the divergence is a shared number rather than an argument. You cannot create a variable by asking, but you can stop the invisible one from being deniable.
- How is a ranked-scope commitment different from simply promising less?It commits to the same outcome while separating what must exist from what would be better. The sponsor keeps the decision rights — they reorder the ranked remainder every iteration — so they are not buying a smaller product, they are buying the ability to spend the remaining capacity on whatever is most valuable once real evidence exists. Promising less lowers the ceiling; ranking moves the choice later, to where it is better informed.
- What early signal tells you a programme is already in this failure mode?Findings from real use that are recorded and never scheduled. If each iteration produces observations that never change what happens next, feedback is decorative and the scope is effectively closed regardless of what the process is called. Two supporting signals: iteration boundaries whose only question is whether the plan is on track, and a growing set of accepted workarounds that nobody has costed.
It is a budget with a fixed income, a fixed shopping list and a fixed spending limit: the arithmetic still has to balance, so it balances by quietly buying the cheaper ingredients.
saying these in an interview costs you the question
- Believes all three corners can be fixed without consequence
- Never mentions quality as the unnamed fourth lever
- Proposes working harder or longer hours as the fix
- Confuses ranked scope with simply committing to less
- Treats the date as always negotiable, ignoring seasonal or external windows
- Escalates the problem with no options attached to it