Sprint Tracking in Scrum: Burndown, Burnup and Progress

Sprint tracking helps a Scrum Team understand how work is progressing during a Sprint.

Scrum does not require a specific tracking chart. Teams may use tools such as Burndown, Burnup or Cumulative Flow when they find them useful.

Why Track Sprint Progress?

The purpose is not to create a performance score. It is to help the team inspect progress and identify situations that may require adaptation.

  • Understand remaining work.
  • Identify unexpected changes.
  • Spot potential delays.
  • Support conversations during the Sprint.
  • Improve future planning.

1. Burndown Chart

A burndown chart shows the amount of work remaining over time.

Burndown

Work Remaining ↓ as the Sprint progresses

If the amount of remaining work is not decreasing as expected, the team can investigate why.

Simple Burndown Example

Day Work Remaining
Day 1 40 points
Day 3 32 points
Day 5 22 points
Day 8 10 points
Day 10 0 points

2. Burnup Chart

A burnup chart shows work completed over time and can also show the total scope.

Burnup

Work Completed ↑ as the Sprint progresses

Burnup charts can be particularly useful when scope changes, because the total scope can be shown separately from the amount completed.

Burndown vs Burnup

Burndown
Burnup
Shows work remaining.
Shows work completed.
Line generally moves downward.
Line generally moves upward.
Simple view of remaining work.
Can show completed work and changing scope separately.

3. Cumulative Flow

A cumulative-flow diagram shows how work moves through different workflow stages over time.

It can help reveal growing queues, bottlenecks and excessive WIP.

Example:

If the "Testing" section continues to grow while the "Done" section remains small, the team may have a bottleneck in testing.

What Should a Scrum Master Look For?

Flat Progress Little or no change in completed or remaining work.
Scope Changes The amount or nature of work changes during the Sprint.
Late Completion Most work reaches Done near the end of the Sprint.
Repeated Pattern Similar tracking problems occur across multiple Sprints.

What Should the Scrum Master Do?

A Scrum Master should use tracking information as a conversation starter.

For example, if progress remains flat for several days, useful questions might be:

  • Is there an impediment?
  • Are items too large?
  • Is too much work being started?
  • Has our understanding of the work changed?
  • Are we still progressing toward the Sprint Goal?
Important:

A chart does not tell you the reason behind a trend. The team needs inspection and discussion to understand what the data means.

Don't Use Charts to Judge Individuals

Sprint charts should help the team understand its work. They should not be used to rank Developers or measure individual productivity.

A sudden change in a chart may have many causes, including scope changes, dependencies, technical problems or improved understanding.

Are Burndown Charts Mandatory?

No.

Scrum does not require burndown or burnup charts. They are optional practices that teams can use to support inspection and forecasting. :contentReference[oaicite:2]{index=2}

Key Takeaway

Sprint tracking is useful when it helps the Scrum Team understand its progress and make better decisions.

The objective is not to make the chart look good. The objective is to make the real situation visible.