Running agile delivery inside a fixed budget
Fixed budgets and iterative delivery are compatible if scope is the variable. Fixing all three is what causes trouble.
ZooBieDoo Infotech Engineering TeamRead
Key takeaways
- Escalate early with options; delay narrows what is possible.
- Report outcomes, changes, risks and required decisions.
- Bring options and a recommendation, not just a problem.
- Confirm decisions in writing to prevent disputes about the past.
Bad news does not improve with age
The instinct when a project slips is to wait for the next sprint, hoping to recover. The delay is what converts a manageable problem into a crisis, because options narrow as time passes.
Raising an issue early, with options attached, is treated as competence. Raising it late is treated as concealment, regardless of intent.
Report in outcomes, not activity
Stakeholders do not need velocity charts. They need to know what now works, what has changed since last time, what is at risk, and what decision is needed from them.
- What is working in production now.
- What changed since the last report.
- What is at risk, with impact and options.
- What decision you need, and by when.
Bring options, not just problems
“We are behind” invites anxiety. “We are two weeks behind; here are three options with their trade-offs, and my recommendation” invites a decision.
Framing this way keeps the conversation productive and demonstrates that the situation is understood rather than merely reported.
Keep a written record
Decisions taken verbally are remembered differently by different people, particularly under pressure. Confirming decisions and their reasoning in writing is not bureaucracy; it is what stops a disagreement about the past derailing the present.
Circulate short summaries after significant meetings. It takes minutes and repeatedly saves days.
Communicating during an incident
Incident communication has different requirements from project reporting: frequency matters more than completeness, and silence is interpreted as loss of control.
Send brief updates at a stated interval even when there is nothing new — “still investigating, next update in thirty minutes” is genuinely useful. State impact in user terms, what is being done, and when the next update comes.
Avoid speculating about cause while resolution is in progress. Early theories are frequently wrong, and a corrected explanation costs more credibility than a delayed one.
Frequently asked questions
Frequently enough that nothing is a surprise usually a short weekly note and a fuller review each increment. Sporadic reporting is where surprises come from.
Present it factually with options and record it. A supplier who withholds problems to preserve the relationship damages it far more when the problem surfaces.
Whoever sees the problem, through an agreed path. Escalation routes that depend on hierarchy are slow, and by the time they complete the options have narrowed.
