Work Tracking: Burnup Chart vs Burndown Chart Interpretation

PMBOK v8 Definition

A burnup chart tracks the amount of work completed compared to the expected work that should be done within a predefined interval. It shows how much work has been completed and how much remains. In contrast, a burndown chart shows how much work is yet to be completed over time. These charts are tools used in agile project management for monitoring progress against the planned work.

Why It Matters for the Exam

The PMI exam frequently tests your ability to distinguish between burnup and burndown charts, as they are commonly confused concepts. Questions appear in the Monitoring and Controlling process group, particularly in scenarios involving agile/adaptive project environments. Expect situational questions where you must select the correct chart type based on what information the project manager needs to communicate.

Key Points to Remember (for the exam)

• Burnup Chart: Shows how much work has been completed AND how much work remains. Two lines: one for total scope, one for completed work.
• Burndown Chart: Shows how much work is yet to be completed. One line trending downward toward zero.
• Combined Burn Chart: Shows both completed and remaining work in a single view.
• Primary Purpose: Track progress within a predefined interval (iteration, sprint, or timebox).
• Common Confusion: Burnup shows progress upward (work done increasing), burndown shows remaining work decreasing.
• Key Distinction: Burnup helps identify scope changes (total scope line shifts), burndown focuses on completion rate.
• Exam Tip: If the question mentions "scope creep" or "scope changes," burnup is likely the correct answer because it shows total scope changes.

Typical PMI Exam Example

A project manager is reporting to stakeholders on an agile project. The team completed 45 story points this sprint, but the product owner added 10 new story points to the backlog. The project manager needs to show both the work completed AND the total scope change. Which chart should be used?

Answer: Burnup chart, because it displays both completed work and the total scope line, allowing stakeholders to see scope additions.

PMI Exam Traps

• Trap: Confusing burnup with burndown charts

  • Reality: Burnup shows work completed (ascending) and total scope; burndown shows remaining work (descending)

• Trap: Thinking both charts show the same information

  • Reality: Burnup reveals scope changes (total line moves), burndown does not clearly show scope additions

• Trap: Selecting burndown when scope changes need visibility

  • Reality: Burndown only shows remaining work; scope increases make the burndown line go up, confusing interpretation

• Trap: Assuming these charts apply only to software projects

  • Reality: Any project using iterative/adaptive approaches can use burnup/burndown charts

Important PMI Connections

Quick Review Questions

1. A burnup chart shows two lines. What does each line represent?

2. During a sprint review, the product owner added 5 new user stories. Which chart would best communicate this scope change to stakeholders?

3. A burndown chart shows the line going upward instead of downward. What does this indicate?

4. Your team completed 30 story points in a 2-week iteration. Which concept measures the rate at which deliverables are produced?

5. What is the key difference between a combined burn chart and a standard burnup chart?

PMBOK v8 Reference

Section 5 – Tools and Techniques, pages 213-214 Figure 5-26: Burnup Chart (referenced in PMBOK v8 context) Schedule Development Steps: Section 2.4, Figure 2-23 (Define Activities, Determine Sequence, Estimate Effort and Duration, Adjust)