How to read chart

Burnup vs burndown

The functionality of both types of charts is identical. The only difference is your visualization preference (whether you want to see the chart going up or down):

Track progress towards work scope completion

On the chart you can see the following information:

Completed work:
- #1 - the chart that is growing as the amount of work completed is growing
- #2 - the total amount of work completed at this moment of time
Active sprints:
- #3 - current one or several active sprints
- #4 - total amount of work taken into currently active sprints
Remaining work:
- #5 - the amount of work still remaining to complete
- #6 - current total amount of remaining work
Total work:
- #7 - the chart showing the dynamics and the changes in total work scope
- #8 - current amount of total work

Past performance forecasting scenario

When the chart is built, by default you see the chart based on team’s past performance scenario:

Let’s check forecasts based on average team performance. Look at the numbers on the chart above:

#1 - the forecast is based on team’s performance during last 6 sprints
#2 - the average velocity (in our case velocity is measured in Story Points) is equal 23.33 Story Points per sprint
#3 and #4 - based on the past average velocity, the remaining work scope is to be delivered by 15/03/2025
#5 - based on the past average velocity, the remaining work scope will take 6 sprints for the team

What-if scenario

By clicking #1 “Scenarios” button and #2 you can specify two alternative scenarios:

What-if velocity - answers the question “what will be the delivery date be if the given team’s velocity is equal to a specified one?”
What-if date - answers the question “what should be team’s velocity if the deadline date is set?”

You can specify up to 10 what-if scenarios and instantly see them on and below the chart:

Scenarios can be easily switched off however saved for further use:

Backlog growth scenario

You can forecast work scope completion scenarios for a custom backlog size or even take into account the scope that is constantly growing (e.g., you may account for undiscovered work, or take into account bugs that will definetely emerge):

#1 - specify a custom amount of remaining work and check different forecasts for it
#2 - specify how many story points are added to existing work scope each sprint and check different forecasts that account for this scope growth

Choose what work scope you want to forecast

Use past performance of your teams and forecast any scope by searching it with JQL:

Visualise deadlines with target lines

Specify the deadline date (#1 on the chart) and see it on the chart (#2):

Get into the details of completed work

See a multi-level breakdown of completed work by any Jira field

On the chart click on the area (#1 on the picture below) related to past or active sprints and get the detailed data broken down by any Jira issue field:

On the chart above you see one-level breakdown for the Sprint 58:

#3 - shows breakdown of completed work by issue types
#4 - shows breakdown of work scope changes by issue types

By clicking #2 choose up to two levels of breakdowns:

Analyze completed work issue by issue

When sprint is chosen on the chart, below the breakdown area you can see the list of issues belonging to a particular sprint (for Scrum boards) or a timeframe (for Kanban boards):

Group data by months or quarters

When you deliver big projects that span timeframe of quarters and years, you may want to see the data grouped by month or quarters. Here is how to do it: