Combined committed vs. delivered story points across both teams, all 8 sprints. Used for release forecasting from Sprint 3 onward, once the team's velocity stabilized past the initial ramp-up.
Committed
Delivered
Avg. velocity (Sprints 2–8): 43 pts
Sprint 1 (ramp-up)40 / 34 pts
Sprint 5 (Release 1)48 / 46 pts
Sprint 8 (Release 2)48 / 46 pts
Avg. velocity, Sprints 2–843 pts
Predictability (delivered/committed)~94%
Reading This Chart
- Sprint 1 under-delivered relative to commitment (85%) — a normal ramp-up sprint as both teams established their working rhythm; this is why velocity forecasting used Sprints 2–8, not Sprint 1, as the baseline.
- From Sprint 2 onward, delivered points stayed consistently close to committed (predictability ~94%), which is what let C. Tyrrell forecast the Release 2/cutover date with confidence heading into Sprint 7.
- Sprint 7 (data migration-heavy) shows the widest single-sprint gap between committed and delivered outside of Sprint 1 — consistent with Anchor's heavier, higher-uncertainty migration workload that sprint.