What a sprint burndown is
A burndown chart plots remaining work against days elapsed, with an ideal straight line for comparison. The gap between your actual line and the ideal one is the story: consistently above means the sprint is over-committed, a flat stretch means work is blocked.
When to use one
- Running sprint reviews and retrospectives with evidence rather than impressions
- Spotting mid-sprint that the commitment will not land, while there is still time to act
- Showing a delivery manager the shape of a team's week without a status meeting
The data format
One point per line: Day, RemainingWork.
Paste rows like this — copy the example straight into the builder to see it render:
0, 80 1, 72 2, 66 3, 50 4, 44 5, 30 6, 18 7, 6
How to make one
- Paste your data into the Studio, or upload a CSV or XLSX file.
- Set your colours — by hand, from pasted brand hex codes, or extracted from your logo.
- Generate and export as PNG or SVG for your deck or report.
One thing people get wrong. A burndown that only moves on the last two days is not a scheduling problem, it is a batch-size problem. Read the shape, not just the endpoint.
Why it runs in your browser
Charts are parsed and drawn entirely on your own device. No rows, files or logos are uploaded, so a sprint burndown built from confidential project or process data never touches a server. You can verify it: open your browser's network tab while you generate one.