How to Create and Read a Burndown Chart
What Is a Burndown Chart?
A burndown chart visualizes the remaining work in a sprint over time. The horizontal axis shows days, the vertical axis shows remaining effort (story points or task count), and a single line tracks how work "burns down" from start to finish.
Purpose
- See sprint progress at a glance
- Detect early whether the team is on track to finish
- Provide an objective view of the team's pace
- Give daily standups a concrete discussion point
Chart Structure
A burndown chart consists of two main lines.
The Ideal Line (Plan Line)
A straight line drawn from the total points at sprint start down to zero at sprint end. It represents the "ideal pace" if work were consumed evenly every day.
Example: 2-week sprint, 40 total points
Daily burn rate = 40 ÷ 10 business days = 4 points/day
Day 0: 40 points
Day 1: 36 points
Day 2: 32 points
...
Day 10: 0 points
The Actual Line
The real remaining work plotted day by day. It drops each time a story or task is marked complete.
The relationship between these two lines tells you the sprint's health.
| Actual Line Position | Meaning |
|---|---|
| Below the ideal line | Ahead of schedule |
| On the ideal line | On track |
| Above the ideal line | Behind schedule |
How to Build a Burndown Chart
Step 1: Gather Initial Data
Collect the following from sprint planning.
| Item | Example |
|---|---|
| Sprint duration | 2 weeks (10 business days) |
| Start date | 2026-03-09 (Monday) |
| End date | 2026-03-20 (Friday) |
| Total story points | 40 points |
| Stories in sprint | 8 stories |
Step 2: Draw the Ideal Line
Draw a straight line from the total points on Day 0 to zero on the last day. Use business days (exclude weekends and holidays).
Step 3: Record Remaining Work Daily
At each daily standup (every morning), record the remaining story points.
Day 0 (Mon): 40 ← Sprint start
Day 1 (Tue): 40 ← No stories completed yet
Day 2 (Wed): 35 ← 5-point story completed
Day 3 (Thu): 35 ← No completions
Day 4 (Fri): 27 ← 8-point story completed
Day 5 (Mon): 27 ← After the weekend
Day 6 (Tue): 22 ← 5-point story completed
...
Step 4: Plot the Actual Line
Plot the recorded values as a line graph alongside the ideal line. The visual comparison makes progress (or lack thereof) immediately obvious.
Reading Common Patterns
Burndown charts produce recognizable patterns that reveal the team's state.
Pattern 1: Steady Descent
The actual line closely follows the ideal line in a smooth downward slope.
Points
40 |*
| *·
| ·*
| *·
| ·*
| *·
| ·*
0 |-------*→ Days
Ideal(·) and Actual(*) nearly overlap
Meaning: The team is consuming work at a consistent pace. Sprint planning was well-calibrated.
Pattern 2: Staircase Descent
The line stays flat for days, then drops sharply.
Points
40 |****
| ·
| ****
| ·
| ***
| *
0 |-------→ Days
Meaning: Stories are too large. Work is progressing, but nothing registers as "done" until multi-day stories finish.
Fix: Break stories into smaller tasks that can be completed in 1–2 days.
Pattern 3: Flat Start, Late Rush
Little progress in the first half, then a steep drop in the second half.
Points
40 |*********
| ·
| *
| *
| *
| *
0 |-------→ Days
Meaning: The team spent the first half on design, setup, or investigation. Alternatively, the definition of done is so strict that intermediate work doesn't register.
Fixes:
- Complete technical spikes before the sprint starts
- Clarify acceptance criteria so partial completions can be tracked
- Split stories by layer (frontend, backend) to enable incremental completion
Pattern 4: Scope Creep (Line Goes Up)
Remaining work increases during the sprint.
Points
40 |*
| *
| **
| ***
| **** ← Increasing
|
0 |-------→ Days
Meaning: New work is being added mid-sprint, or original estimates were too low and tasks are expanding.
Fixes:
- Enforce a no-scope-change policy during sprints (agree with PO)
- Defer new requirements to the next sprint
- Improve estimation through retrospective reviews
Pattern 5: Significant Work Remaining at Sprint End
A large amount of points remain on the final day.
Points
40 |*
| ·*
| ·*
| ·*
| ·*
| ·*
20 | ·* ← 20 pts left on final day
0 |-------→ Days
Meaning: The sprint was overloaded beyond the team's capacity.
Fix: Base sprint capacity on historical velocity. Plan to roughly 80% of average velocity.
Building a Burndown Chart in a Spreadsheet
You don't need specialized tools. A spreadsheet works well.
Data Table Layout
| Date | Business Day | Ideal Remaining | Actual Remaining |
|---|---|---|---|
| 3/9 | Day 0 | 40 | 40 |
| 3/10 | Day 1 | 36 | 40 |
| 3/11 | Day 2 | 32 | 35 |
| 3/12 | Day 3 | 28 | 35 |
| 3/13 | Day 4 | 24 | 27 |
| 3/16 | Day 5 | 20 | 27 |
| 3/17 | Day 6 | 16 | 22 |
| 3/18 | Day 7 | 12 | 17 |
| 3/19 | Day 8 | 8 | 10 |
| 3/20 | Day 9 | 4 | 5 |
| 3/21 | Day 10 | 0 | 0 |
Charting Steps
- Set "Business Day" as the X-axis, "Ideal Remaining" and "Actual Remaining" as Y-axis series
- Choose a line chart
- Style the ideal line as dashed, the actual line as solid
- Fix the Y-axis minimum to 0
Using Burndown Charts in Daily Standups
The burndown chart anchors standup discussions with objective data.
What to Check
- Actual vs. ideal: If behind, discuss what's causing the delay
- Extended flat periods: Look for blockers preventing story completion
- Sudden changes: Detect scope changes or estimation misses early
Ground Rules
- The chart is a team health check, not an individual performance metric
- When behind, discuss "What can we do?" not "Whose fault is it?"
- Chart updates are a shared team responsibility
Limitations of Burndown Charts
Burndown charts are useful but have blind spots.
Scope Changes Are Invisible
A drop in remaining work could mean "tasks completed" or "tasks removed." In projects with frequent scope changes, consider supplementing with a burn-up chart (which tracks completed work separately from total scope).
Quality Is Not Reflected
A smoothly descending chart doesn't guarantee quality. Define a clear Definition of Done and manage quality alongside the numbers.
The "Why" Is Missing
The chart shows what is happening, not why. When the chart signals a problem, the team needs conversation to identify root causes.
Summary
A burndown chart is a simple, effective way to visualize sprint progress. The relationship between the ideal and actual lines reveals the team's state at a glance: staircase patterns suggest stories need splitting, upward trends signal scope creep, and late rushes indicate front-loaded work. Whether built in a spreadsheet or a dedicated tool, burndown charts make daily standups concrete and help teams detect problems early. Understand the chart's limitations—it won't show scope changes or quality—and pair it with team dialogue for the full picture.