Burndown Chart,
Generated.
Paste daily remaining story points. Get a clean burndown SVG with ideal line, completion %, and a pattern diagnosis (on-track, hockey-stick, late slip, under-delivery).
Enter your sprint data
Tip: If your tracker shows daily totals, paste them straight in. We render the ideal line from your starting points and sprint length automatically.
Don't generate a burndown; have one
SprintFlint draws the burndown live every time a ticket moves. No daily totals to type, no spreadsheet to maintain.
Start Free, 300 Tickets IncludedLooking for the concept, not the tool? Read the Burndown Chart glossary entry.
Burndown chart FAQ
What does the ideal line represent?
It's a straight line from your starting points down to zero across the sprint length; the rate you'd burn down if you cleared an equal slice of work each day. Real sprints don't burn down linearly; the ideal line is just a reference, not a target. More in the burndown chart glossary entry.
Why is the actual line above the ideal in the early days?
Almost always. Most teams start by exploring the work (designing, branching, refining) before stories actually close. A flat early-sprint line is normal. If it stays flat past mid-sprint, that's the warning sign.
What's a hockey-stick burndown?
The line stays flat or close to flat through most of the sprint, then drops sharply on the last 1-2 days. Usually means several large stories all completed at once, often with rushed reviews. The pattern correlates with sprint commitment too aggressive for the team's size, or stories not split small enough; try the Story Splitter on the largest one.
Should I use story points or hours?
Story points. Hours-based burndown drifts because engineers don't reliably log hours, and hours don't account for story-size relativity. Points-based burndown is what most healthy teams use. (See how the major estimation techniques compare.)
Why does my burndown go up some days?
You added scope mid-sprint. Either points were re-estimated upward as work was discovered, or stories were brought in. Both happen. Tracking the spike at retro is more useful than hiding it.
Should I share this externally?
Yes; the SVG download is small and renders crisply in any document, retro template, or update email. Drop it into your sprint review or async update.
Pair with the rest of the sprint analytics
Velocity calculator, sprint forecaster, capacity calculator. All free, all client-side.
Want this built into your sprint board?
SprintFlint surfaces velocity, capacity, burndown, and cycle time automatically; no calculator, no spreadsheet, no plugin maze. Free for the first 300 tickets. No credit card.