Burnup Charts help Scrum Teams:

• Track work completed over time
• Visualize scope changes clearly
• Forecast delivery timelines
• Improve transparency
• Support better release planning

Key Components of Burnup Chart

Component	Description
X-Axis	Time (days, sprints, or iterations)
Y-Axis	Work units (Story Points / Tasks / Hours)
Total Scope Line	Total planned work (may change over time)
Completed Work Line	Work completed by the team

How Burnup Chart Works

At the start:

• Completed work = 0
• Total scope = full backlog

As the team completes work:

• The completed work line moves upward

If scope changes:

• Total scope line moves up or down

Completion is reached when:

• Completed work line meets total scope line

Example of Burnup Chart

Example:

Day	Completed Story Points	Total Scope
Day 1	0	40
Day 2	5	40
Day 3	10	45 (scope added)
Day 4	18	45
Day 5	30	45
Day 6	45 ✅	45

The chart clearly shows both progress and scope changes.

Burnup Chart vs Burndown Chart

Aspect	Burnup Chart	Burndown Chart
Focus	Work completed	Work remaining
Scope Changes	Clearly visible	Less visible
Lines	Two lines (scope + completed)	One main line (remaining work)
Transparency	High	Medium
Interpretation	Easier when scope changes	Easier for fixed scope

When to Use Burnup Chart

• When scope changes frequently
• For long-term tracking (release level)
• When stakeholders need better visibility
• When working with evolving product backlog

How Burnup Chart is Used in Scrum

During Sprint

• Tracks completed work daily
• Shows progress clearly

During Release Planning

• Tracks work across multiple Sprints
• Helps forecast completion

For Stakeholders

• Provides clear view of progress and scope changes
• Improves transparency

Benefits of Burnup Chart

Benefit	Description
Clear Visibility	Shows both progress and scope
Handles Scope Changes	Easily shows added or removed work
Better Forecasting	Helps predict delivery timeline
Improved Transparency	Stakeholders understand progress easily
Motivation	Shows increasing completed work

Common Patterns in Burnup Chart

Steady Growth

• Consistent upward movement
• Indicates healthy progress

Flat Line

• No progress
• Possible blockers

Sudden Jump in Scope

• New work added
• Scope change

Slow Progress

• Gradual increase
• May indicate inefficiencies

Role of Scrum Master

The Scrum Master:

• Ensures chart is updated regularly
• Explains chart to team and stakeholders
• Identifies trends and issues
• Facilitates discussions based on data
• Supports improvement actions

Role of Product Owner

The Product Owner:

• Tracks scope changes
• Uses chart for release planning
• Communicates progress to stakeholders

Role of Developers

Developers:

• Complete work consistently
• Update progress regularly
• Support achieving Sprint goals

Limitations of Burnup Chart

• Requires accurate updates
• Does not show task-level detail
• May become complex for large projects
• Needs interpretation for decision-making

Best Practices

• Update chart regularly (daily or per Sprint)
• Use consistent estimation units
• Track scope changes clearly
• Use along with other Agile metrics
• Analyze trends, not just numbers

Common Mistakes

• Not updating completed work regularly
• Ignoring scope changes
• Using incorrect estimation units
• Misinterpreting progress trends
• Using it as a performance tool

Real-Life Example

A Scrum Team building a banking application uses a Burnup Chart:

• Initial scope: 100 Story Points
• After Sprint 2: scope increases to 120
• Completed work progresses gradually
• Final completion when completed line meets scope line

The Burnup Chart clearly shows:

• Progress made each Sprint
• Impact of scope changes
• Realistic delivery timeline

Conclusion

A Burnup Chart is a powerful Agile metric that provides better visibility into both progress and scope changes compared to a Burndown Chart.

It is especially useful for dynamic projects where requirements evolve frequently, helping Scrum Teams and stakeholders maintain transparency, improve forecasting, and deliver value successfully.