Cumulative points delivered against total program scope, across the full 8-sprint program. Unlike a sprint burndown (which resets each sprint), a burnup tracks the whole release and shows when scope itself changes — the small step-up after Sprint 3 reflects a re-estimation, not scope creep from new features.
Total scope (points)
Cumulative delivered
Release milestone
Reading This Chart
- Total scope moved from 339 to 342 points after the Sprint 3 Backlog Refinement re-estimation (MCM-123's screen-share entitlement finding) — a controlled, documented scope change, not silent creep.
- By Sprint 5 (Release 1), 205 of 342 points were complete — the release didn't wait for 100% of total scope, only for the Release 1-scoped Epics/Features to be done, per the Vision & Roadmap's Now/Next split.
- By Sprint 8 (Release 2/cutover), 337 of 342 points were delivered. The remaining 5 points (MCM-145, the read-only archival export) were formally carried to the post-program candidate backlog — see Sprint Backlogs and, later, the Program Closeout.