Burndown and Burnup Charts

Burndown and Burnup Charts

Introduction: Why This Matters

Agile teams need clear, visual ways to track progress toward sprint and release goals. Burndown and burnup charts provide that visibility. They show how much work remains (burndown) or how much has been completed (burnup) over time. Both charts make progress transparent, help identify risks early, and build stakeholder confidence.

On the PMP exam, these charts often appear in situational questions about progress tracking, forecasting, or stakeholder communication. In practice, they help teams adapt quickly when velocity or scope changes.

Purpose and Objectives

Primary Purpose: To visualize progress and support forecasting.

Key Objectives:

  • Define burndown and burnup charts and explain their differences.
  • Interpret chart trends to identify risks or delays.
  • Recognize when scope changes impact tracking.
  • Apply these charts to situational PMP exam questions.
  • Communicate progress effectively with stakeholders.

Overview

Burndown and burnup charts are lightweight, visual tracking tools that help teams and stakeholders see progress over time and respond quickly when trends shift.

  • Burndown: Shows work remaining versus time, often used at the sprint level.
  • Burnup: Shows work completed versus total scope, making scope changes visible.

Characteristics

  • Time-based trending: Both charts visualize progress across a defined time period.
  • Forecasting support: Trend lines help estimate whether targets will be met.
  • Risk visibility: Flat or adverse trends signal issues early.
  • Scope awareness (burnup): Scope changes show up clearly through a moving scope line.
  • Transparency: Helps align expectations and reduce “surprise” outcomes.

Practical Example

Context: A Scrum team is delivering a mobile payment feature and needs sprint and release visibility.

Activities:

  • Burndown: At the start of a 2-week sprint, the team has 50 story points. After 1 week, only 10 points are completed. The chart shows a flat trend, signaling the sprint goal is at risk.
  • Burnup: Across a 10-sprint release, the burnup chart shows steady progress until sprint 6, when scope increases from 200 to 240 story points. Stakeholders immediately see why completion will take longer.

Outcome: Burndown alerts the team to sprint-level issues. Burnup gives leadership clarity on how scope changes affect long-term goals.

Common Pitfalls

Relying Only on Burndown

  • Pitfall: Scope changes can be hidden, making progress look worse or better than reality.
  • Prevention: Use burnup (or add scope indicators) when scope changes are likely.

Failing to Update the Charts

  • Pitfall: Outdated data breaks transparency and erodes trust.
  • Prevention: Update daily, and ensure “done” is consistent with the team’s Definition of Done.

Overreacting to Normal Variation

  • Pitfall: Treating every fluctuation as a crisis.
  • Prevention: Watch trends over time and investigate repeated patterns, not single-day spikes.

Using Charts to Pressure Teams

  • Pitfall: Turning charts into tools for micromanagement.
  • Prevention: Use charts for collaboration, planning, and transparency, not punishment.

Sensei Tip : If stakeholders are worried about shifting scope, lead with a burnup chart. It shows progress and scope changes in one view, so the story stays honest and calm.

Exam Alert : Wording matters. Sprint-focused progress usually points to burndown. If the question mentions scope changes or “progress is not visible due to scope shifts,” burnup is typically the best answer.

Exam Lens

Patterns on the PMP Exam:

  • Burndown appears in sprint-focused questions.
  • Burnup appears in release or scope-change scenarios.
  • Watch for wording like “progress is not visible due to scope change.” That is a burnup cue.

Sample Question

Question: A project team has completed 80 story points, but total scope increased from 200 to 220 points mid-project. Which chart best shows both progress and scope change?

  1. Burndown chart
  2. Burnup chart
  3. Velocity chart
  4. Cumulative flow diagram

Correct Answer: B. Burnup chart.

Quick Recap Table

Chart Tracks Best Use Exam Watch Point
Burndown Work remaining vs time Sprint tracking Hides scope changes
Burnup Work completed vs total scope Release tracking Makes scope changes visible

Key Takeaways

  • Burndown charts track remaining effort, useful for short-term sprint monitoring.
  • Burnup charts track both completed work and scope, making them ideal for release tracking.
  • Burnup is better for showing scope changes. Burndown is simpler for daily sprint tracking.
  • On the exam, look for context clues: sprint focus points to burndown; scope visibility points to burnup.
  • In practice, teams often use both together for maximum transparency.

Next Step

With burndown and burnup charts explained, we now move into Retrospectives, the Agile practice that ensures continuous team improvement.

Scroll to Top