Burnup Chart

A Burnup Chart is an agile visualization tool that graphically represents two primary curves: completed work and total project scope. Unlike a burndown chart that only shows remaining work, the burnup chart offers a more comprehensive view by clearly distinguishing scope changes from productivity variations. This tool becomes indispensable in environments where scope evolves frequently, enabling teams and stakeholders to make informed decisions based on objective data.

Fundamentals

• Two axes: horizontal axis represents time (sprints, weeks), vertical axis represents work volume (story points, hours, tickets)
• Two distinct curves: upward line of completed work and total scope line that can vary
• Complete transparency: every scope change is immediately visible, unlike metrics that mask these variations
• Completion projection: distance between the two curves enables estimation of probable delivery date based on observed velocity

Benefits

• Scope creep visibility: immediate identification of scope additions impacting delivery date
• Team motivation: always-ascending completed work curve highlights achievements rather than focusing on remaining tasks
• Improved predictability: average velocity enables accurate projection of current scope completion date
• Data-driven conversations: facilitates objective discussions with stakeholders about scope/time/resource trade-offs
• Strategic alignment: helps prioritize features by visualizing each addition's impact on overall timeline

Practical Example

Imagine a mobile app redesign project initially estimated at 200 story points over 10 sprints. After 4 sprints, the team has delivered 85 points (average velocity of 21.25 points/sprint). Meanwhile, critical new features were added, raising scope to 250 points. The burnup chart immediately reveals that:

• Velocity is stable and predictable (approximately 21 points/sprint)
• Scope increased by 25% (from 200 to 250 points)
• At current pace, approximately 8 additional sprints needed (165 remaining points ÷ 21 points/sprint)
• Growing gap between curves signals need for arbitration: increase resources, descope features, or accept extended timeline

Implementation

1. Define consistent measurement unit: story points, ideal hours, or ticket count based on team maturity
2. Establish initial scope baseline: document starting perimeter with complete estimation
3. Update at regular frequency: ideally at end of each sprint or iteration to maintain accuracy
4. Plot both curves: report cumulative completed work and total scope (including additions/removals)
5. Calculate projection: extend completed work curve trend to estimate convergence date
6. Analyze variations: identify causes of velocity changes (vacations, dependencies, technical debt)
7. Communicate insights: share chart in sprint review and steering committee with contextual interpretation

Related Tools

• Jira: automatic burnup chart generation from Scrum boards with customizable filters
• Azure DevOps: configurable burnup widgets in dashboards with data export
• Linear: native progress visualizations with integrated velocity metrics
• Miro/Mural: collaborative manual burnup chart creation for workshops and retrospectives
• Google Sheets/Excel: automatic calculation templates with dynamic charts for teams without dedicated tools

The burnup chart transforms project management from a reporting exercise into a strategic steering tool. By making both progress and scope evolution visible, it enables delivery teams to demonstrate their real value while facilitating necessary trade-offs with stakeholders. In a context where agility means embracing change, this tool becomes the common language between technical execution and business vision.