Look closely at most "surprise" slips in a delivery portfolio and they share a property: the data knew first.

The story points were already there. The child work already ran past the parent's due date. The estimate on the initiative had already been overtaken by the features beneath it. None of it was hidden.

Why nobody saw it

The information existed, but it was never assembled. In most organisations:

  • The plan lives in one place — a roadmap, a slide, a portfolio spreadsheet — owned by programme or portfolio managers.
  • The backlog lives in another — the work tracker — owned by delivery teams.
  • They are reviewed on different cadences. Teams look at the backlog every sprint. The plan gets revisited monthly or quarterly.
  • They are reviewed by different people. The people who see the work growing are not the people presenting the date.

No step in the process puts the two numbers side by side. Each group sees a version of the truth that looks fine from where they stand.

How it surfaces

So the gap grows quietly until it appears in a governance meeting, presented as news. By then it is weeks or months old, and the options for dealing with it are narrower and more expensive than they would have been.

It was never news to the data. Only to the room.

Making the comparison routine

The fix is less about tooling than about cadence and ownership:

  1. Name the comparison. Decide that "plan versus current backlog" is a check that happens, not something people notice by accident.
  2. Give it an owner. Someone is responsible for running it and raising what it finds.
  3. Run it more often than the governance meeting. If the check only happens just before steering, it will always produce surprises at steering.
  4. Report the gap, not just the status. A status says whether a date has moved. A gap says whether the work still fits inside it.

Organisations that do this rarely get surprised in steering meetings. They have the same slips as everyone else. They just learn about them while they are still small.

Tags: #DataDrivenDelivery #PortfolioManagement #AgileDelivery