When the Plan and Reality Diverge

Midway through a release cycle our sprint velocity and dependency data started telling a different story than our original commitment. The integration work was slipping and the gap between what leadership expected and what the data showed was widening.

Rather than wait for the gap to become a crisis I brought it forward early. I pulled together sprint velocity trends, dependency mapping and a risk register update into a clear RAG status report. Then I built an options paper for leadership with two real choices, slip the release date or descope certain features and ship on time.

I presented both options with their trade offs laid out plainly, no hedging and no burying the bad news. Leadership chose to descope. We delivered a stable release on the original date and I followed up immediately with a plan for the deferred scope so nothing fell through the cracks.

This is the kind of decision I try to bring to every programme. Data should drive the conversation, not opinions or optimism. And when you give stakeholders a clear choice instead of a vague warning, they can actually decide.