The PERT Chart Gave the Date a Probability Once. Nobody Re-Ran It.
A PERT chart puts a probability on a finish date once, from the network known on planning day. Keep that probability live against the committed date, in days.
The Critical Path Method Finds the Longest Chain Once. The Chain Keeps Changing.
The critical path method finds the longest chain of dependent work once. After the vote the chain changes. See what that costs the committed date, in days.
The Scope Statement Draws the Boundary. It Doesn’t Watch It Move.
A scope statement records what is in and out of a release, once. It never says what an item crossing that line costs your committed release date. How to read that gap, in days, in Jira.
The Risk Register Scores Likelihood and Impact. It Never Says How Many Days.
A risk register ranks risks by likelihood and impact. It never says how many days a materialising risk costs your committed release date. How to add that number to every review.
The Burn Up Chart Shows the Scope Line Climbing. It Doesn’t Say What That Costs the Date.
A burn up chart shows scope climbing after the confidence vote. It never says what that costs the committed release date in days. Here is how to read both.
The Sprint Review Inspects the Increment. Nobody Re-Prices the Committed Date.
The sprint review inspects the increment and adapts the backlog. It rarely asks what the sprint did to the committed release date. How to add that question, in days.
The Milestone Chart Shows Where the Date Was Placed. Not Whether It Will Hold.
A milestone chart shows where each key date sits on the timeline. It never says how confident anyone should be that the release date will hold. Here is how to read both.
The Velocity Chart Reports Last Sprint. The Committed Date Needs the Next Ten.
The Jira velocity chart shows committed versus completed work per sprint. It never says what that drift costs in days against your committed release date. Here is how to read both.
The Cumulative Flow Diagram Shows the Drift. It Doesn’t Price the Date.
A cumulative flow diagram shows WIP widening and throughput flattening. It never says what that costs in days against your committed release date. Here is how to read both.
Scrum of Scrums Surfaces the Blocker. It Doesn’t Price the Date.
A Scrum of Scrums names cross-team blockers every week, in status terms. The committed release date lives in days. Here is how to price each unresolved dependency against the date, and keep it live between meetings.