Fixed Scope, Fixed Date, Agile Language
A mid-sized insurance company has renamed its project managers to Scrum Masters and its requirements documents to user stories, but governance still runs on quarterly stage gates. You are the Product Owner for a claims portal. At kickoff, the steering committee asks you to sign a plan that fixes scope, budget, and a nine-month delivery date, because procurement has already contracted a vendor on that basis. The team's last four sprints delivered 18, 31, 22, and 27 story points, and two of the largest stories were split only after Sprint Review. The committee says it supports Agile but needs predictability for the board. A senior manager proposes that the team stop changing the backlog after Sprint 2 so the plan stays accurate. The team is willing to work hard but is worried about quality and hidden work.
1. Identify the main ways this operating model contradicts an Agile way of thinking, and explain why renaming roles and artifacts does not make the process Agile.
Read the worked answer
The contradiction is not the existence of budgets or dates; it is the assumption that detailed scope can be known and fixed early while the work remains complex. Agile thinking relies on empirical process control: transparency, inspection, and adaptation. A plan that freezes the backlog after Sprint 2 removes adaptation and turns Sprint Reviews into status meetings rather than learning points. Quarterly stage gates optimize for batch approval and utilization, not for delivering a usable increment early. Renaming roles does not change behavior if decision rights, funding rules, and success measures stay predictive. The velocity data already shows variability, and the late splitting of large stories shows that understanding emerges during delivery. Calling requirements user stories while demanding a fixed specification is a label change, not a mindset change. The practical test is whether the organization can inspect real increments and change its mind based on evidence.
2. How should you respond to the request to commit to fixed scope, budget, and date? Give a concrete negotiation approach.
Read the worked answer
Do not sign a three-way fixed commitment without exposing the trade-off. Separate the constraints: if the date and budget are genuinely fixed, scope must be variable and prioritized. If scope is fixed by contract, the date or cost must carry a range and a contingency. Propose a release plan with a minimum viable scope for the nine-month date, plus deferred and optional scope bands. Use the team's velocity range, not a single number, to forecast how much can be delivered with a stated confidence level. Ask procurement and the vendor what contractual flexibility exists for scope exchange. Offer the board a fixed date with a transparent forecast range and a clearly owned scope trade-off, rather than a false certainty. Document the assumptions and the cost of late change. If the committee insists on all three fixed, escalate the risk explicitly and ask who owns the consequences when reality diverges.
3. Which empirical measures and planning practices would you introduce to give the board meaningful predictability without freezing the backlog?
Read the worked answer
Replace false precision with transparency about range and flow. Track velocity as a range, a release burnup that shows scope changes, cumulative flow for bottlenecks, lead time for backlog items, and escaped defects. Forecast with confidence intervals based on historical throughput rather than a single-point commitment. Use rolling-wave planning: a stable product goal and outcome-based roadmap, with detailed planning only for the next few sprints. At each Sprint Review, show the increment and the evidence it generates. Give the board a one-page view of delivered outcomes, forecast range, top risks, and decisions needed. This provides predictability about how the team works and what it is learning, without pretending that complex work can be specified in advance. The senior manager's freeze proposal should be rejected because it would reduce transparency and delay bad news until it is expensive.