Iteration Burndown Chart: Tracking Work Completion in Adaptive Projects

PMBOK v8 Definition

The Iteration Burndown Chart is a graphical tool that tracks the amount of work remaining in an iteration over time. It displays the remaining effort (typically in story points, hours, or ideal days) on the vertical axis against the iteration timeline on the horizontal axis, showing a downward trend as work is completed. This chart is used primarily in adaptive life cycles to visualize whether the team is on track to complete the planned work within the iteration.

Why It Matters for the Exam

The Iteration Burndown Chart frequently appears in PMI exam questions about monitoring and controlling work in adaptive (agile) environments. You will encounter it in situational questions where the project manager needs to assess progress, identify variances, or communicate status to stakeholders. The exam tests your ability to interpret the chart, understand its relationship to earned value concepts, and distinguish it from the Burnup Chart.

Key Points to Remember (for the exam)

• Primary Purpose: Tracks work remaining (not completed) over time within a single iteration
• Vertical Axis: Work remaining (story points, hours, ideal days)
• Horizontal Axis: Time (iteration days)
• Ideal Trend Line: A straight diagonal line from top-left to bottom-right, representing perfect linear burndown
• Actual Trend Line: The actual work remaining plotted daily; deviations from ideal indicate schedule variances
• Common Interpretation: If actual line is above ideal line → behind schedule; below ideal line → ahead of schedule
• Key Distinction: Shows remaining work versus Burnup Chart showing completed work

Common Confusion: Confusing Burndown Chart (remaining work) with Burnup Chart (completed work). The Burndown Chart focuses on what is left to do; the Burnup Chart focuses on what has been done.

Typical PMI Exam Example

A project manager is using an adaptive life cycle for a software development project. During the third iteration, the team notices the actual burndown line is consistently above the ideal burndown line after five days of a ten-day iteration. What does this indicate?

Answer: The team is behind schedule; more work remains than planned at this point in the iteration.

PMI Exam Traps

• Trap: Confusing the Iteration Burndown Chart with the Release Burndown Chart

  • Reality: The iteration version tracks one iteration; the release version tracks multiple iterations toward a release

• Trap: Thinking a flat or rising burndown line indicates no work is being done

  • Reality: A flat line may indicate work is being added (scope creep); a rising line indicates new work was added exceeding completed work

• Trap: Assuming the Burndown Chart measures budget or cost

  • Reality: It measures effort/work remaining, not financial metrics (use Earned Value Management for cost)

• Trap: Interpreting the chart as showing completed work

  • Reality: The Burndown Chart shows work remaining, not completed work (use Burnup Chart for completed work)

Important PMI Connections

Quick Review Questions

1. What does a Burndown Chart track: work completed or work remaining?

2. If the actual burndown line is below the ideal line on day 4 of a 10-day iteration, is the team ahead or behind schedule?

3. Which chart would you use to show stakeholders the total work completed to date in an iteration?

4. What does a rising burndown line (going up instead of down) typically indicate?

5. Is the Iteration Burndown Chart more commonly used in predictive or adaptive life cycles?

PMBOK v8 Reference

Section 5 – Tools and Techniques, Figure 5-10. Iteration Burndown Chart (pages 175-176)