πŸ“Š

What Is a Sprint Burndown Chart?

A sprint burndown chart is a visual tracking tool that shows how much work remains in a sprint over time. It plots remaining work (Y-axis) against days in the sprint (X-axis), creating a line that ideally burns down to zero by the last day. This simple visualization answers one critical question: "Are we on track to finish?"

πŸ“

Sample Burndown Chart

Story
Points
    β”‚
 40 ●━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ IDEAL LINE
    β”‚ β•²
 35 β”‚  ●
    β”‚   β•²
 30 β”‚    ╲━●━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    β”‚       β•²   ●
 25 β”‚        β•² β•±
    β”‚         ●       ACTUAL LINE
 20 β”‚          β•²
    β”‚           ●
 15 β”‚            β•²
    β”‚             β•²
 10 β”‚              ●━━●
    β”‚                  β•²
  5 β”‚                   ●
    β”‚                    β•²
  0 ●━━━━━━━━━━━━━━━━━━━━●━━━━━━━━━━━━━━━━━━━
    └────┬────┬────┬────┬────┬────┬────┬────┬─
         Day Day Day Day Day Day Day Day Day
         1   2   3   4   5   6   7   8   9  10
βœ“Ideal Line (Gray)

Perfect scenario: burn exactly 4 points per day

●Actual Line (Points)

Reality: varied pace, but trending toward completion

πŸ”¬

Anatomy of a Burndown Chart

Y-Axis (Vertical)

Represents remaining work, measured in story points or hours

Example: 0 at bottom (finished), 40 at top (total sprint)

X-Axis (Horizontal)

Represents time, typically each day of the sprint

Example: Day 1, Day 2... through Day 10 (for 2-week sprint)

Ideal Line

Perfect linear descent if work burned evenly each day

Example: Straight diagonal from top-left to bottom-right

Actual Line

Realityβ€”shows what work remains at end of each day

Example: Jagged line that hopefully trends toward zero

πŸ”

Common Burndown Patterns & What They Mean

Flat Start (Slow Burn)

πŸ“‰
Shape: Horizontal then steep drop

Meaning: Team took time to get started, rushed at end

Common Causes:

  • Stories not ready
  • Blocked tasks
  • Vacation early in sprint
Action: Improve backlog refinement, identify blockers sooner

Scope Increase

πŸ“ˆ
Shape: Line goes UP mid-sprint

Meaning: Work was added after sprint started

Common Causes:

  • Unplanned bugs
  • Scope creep
  • Poor initial estimates
Action: Protect sprint commitment, log additions separately

Healthy Descent

πŸ“‰
Shape: Steady downward trend

Meaning: Team burning work consistently

Common Causes:

  • Clear stories
  • Good collaboration
  • Minimal blockers
Action: Keep doing what you're doing!

Late Spike Down

πŸ”»
Shape: Flat then sudden drop

Meaning: Large story completed late, or optimistic updates

Common Causes:

  • One big story
  • Delayed testing
  • Premature "done"
Action: Break stories smaller, update chart daily
🎯

How Story Points Connect to Burndown

Each completed story reduces the burndown by its point value. Here's a real sprint example:

Day 1 (Mon)
40 pts left

Sprint starts with 8 stories totaling 40 points

Day 3 (Wed)
32 pts left+8 done

Completed 3-point story and 5-point story

On Pace
Day 5 (Fri)
24 pts left+16 done

Finished two 4-point stories

On Pace
Day 7 (Tue)
11 pts left+29 done

Big 13-point story completed!

Ahead!
Day 10 (Fri)
0 pts left+40 done

Last 11 points done, sprint complete

Complete!
βš–οΈ

Burndown vs Burnup Charts

Both track sprint progress, but from opposite perspectives. Here's how they compare:

AspectBurndown ChartBurnup Chart
DirectionStarts high, trends down to zeroStarts at zero, trends up to total scope
FocusWork remaining (what's left to do)Work completed (what we've finished)
Scope ChangesHard to see if scope increasedShows scope line separately from progress
Best ForFixed scope sprints, team motivationDynamic scope, stakeholder reporting

Use Burndown When:

  • β€’Sprint scope is fixed
  • β€’You want to motivate completion
  • β€’Team prefers "countdown" mindset

Use Burnup When:

  • β€’Scope might change mid-sprint
  • β€’You need to show scope creep
  • β€’Stakeholders want completion focus
πŸ’‘

How to Read Your Burndown Chart

Are we on track?

Compare actual line to ideal line. If actual is above ideal, you're behind pace.

Actual > Ideal = Behind | Actual < Ideal = Ahead

When do we update it?

Daily, typically at standup. Update with remaining work, not completed work.

Daily updates = accurate picture

What if we finish early?

Great! Pull in more stories from backlog, or use time for tech debt/learning.

Early finish = capacity to add value

What if we won't finish?

Negotiate scope ASAP. Which stories are must-have vs nice-to-have? Move items out.

Transparency > false hope
🚦

Quick Status Indicators

βœ“

On Track / Ahead

Actual line is at or below ideal line

Remaining ≀ Expected
!

At Risk

Actual line slightly above ideal

1-2 days behind pace
βœ•

Behind Schedule

Actual line well above ideal

Unlikely to finish

βœ“ Key Takeaways

  • 1Burndown charts show remaining work over timeβ€”ideal line is straight, actual line is reality
  • 2Update daily (usually at standup) with remaining story points, not hours worked
  • 3Flat starts and scope increases are warning signsβ€”address them early
  • 4Burnup charts show the same data from opposite angleβ€”better for changing scope
  • 5Use burndown for sprint forecasting and team transparency, not blame

Track Your Sprint Progress Effectively

Start your sprint right with accurate story point estimates using our free planning poker tool.

Start Free Planning Poker Session