Product Team | Six-Sprint Tracker

sprint-tracker-simulated.xlsx — four editable sheets, 429 live formulas, no typed-in results.

1. Tasks — the only place you type. 30 rows (S1–S6, five each) with Task ID, Sprint, Task, Owner Role, Priority, Planned Points, Actual Points, Status, Blocker and Completion Day. Dropdown validation on sprint / role / priority / status, plus a 1–10 check on Completion Day. Two formula columns: Points Variance (Done rows only) and Open Blocker, which feeds the blocker recommendation.

2. Sprint Summary — per sprint and for all six: task counts by status, planned / actual / delivered points, completion rate by tasks and by points, points variance and variance %, estimate variance, blocker rate, a 0–100 risk score with a data bar, and a written readout sentence generated from the row's own numbers.

3. Burndown — 66 rows: every sprint, day 0 to 10. Remaining points = planned points of that sprint's tasks completed on or before that day, so it moves when you edit a Completion Day. Ideal line assumes an even 10-day burn; the Gap column flags behind-schedule days. Two charts: all six sprints overlaid, and Sprint 6 ideal vs actual.

4. Dashboard — 17 live KPIs, the sprint overview table, both charts, and six Sprint 7 recommendations written by formula, so they change with the data.

What the data currently says

Sprint 7 recommendations, as generated: commit 38 points (90% of the 42.8-point average from the four closed sprints); clear the two live blockers — the payment sandbox outage and the PCI sign-off — with owners and exit dates; treat the 8.8% under-run as estimation drift and split anything above 8 points; sequence S6's blocked work first; decide on the one unstarted S6 task; and read the S4→S5 drop (47 → 23 points) as a capacity signal, not a one-off.

How I checked it. Reopened the saved file: 4 sheets, 429 formula cells, zero error tokens, exact label on all four sheets. Recomputed completion-by-points independently from the Tasks rows and matched every sprint exactly. Then rendered the workbook to PDF in LibreOffice and inspected the pages — that pass caught two real defects I fixed: percentages were printing as raw decimals (a number-format argument landed in the wrong parameter), and a KPI label was clipped. Final render shows no clipped text, no chart overlapping a table, no stray zeros.

Limits worth knowing. The risk score is a documented weighted index (45% completion, 20% estimate overrun, 20% blockers, 15% not-started), not a validated predictive model — the bands are stated in the footnote on both sheets. Burndown burns points only when a task is Done, so an in-flight sprint shows a stepped line and a negative variance until work closes. All figures are fictional; nothing here reflects real operations.