Burndown & Burnup Charts is a Jira dashboard app that helps Scrum, Kanban, SAFe®, ITSM, and other teams track completed and remaining work across individual sprints and broader releases.
Compare actual progress with an ideal delivery plan, monitor scope changes, identify whether work is ahead of or behind schedule, and forecast release completion based on the team’s delivery rate. Flexible data sources and calculation methods make it possible to track anything from a single sprint or epic to a cross-project, multi-team release.
The app helps you answer questions such as:
-
How much work has been completed?
-
How much work remains?
-
Is the sprint or release progressing according to plan?
-
Is the scope increasing, decreasing, or remaining stable?
-
Is the team likely to complete the planned work by the target date?
-
When is the release expected to be completed?
-
How is the release expected to evolve if its scope continues to change?
-
Are important release milestones being reached?
-
Which work items are completed and which remain open?
Key features
Two complementary progress tracking charts
Use the Sprint Burndown Burnup Chart to monitor the progress of a specific Scrum sprint.
Use the Release Burndown Burnup Chart to track a longer-term delivery initiative, such as a project release, epic, initiative, theme, or cross-team program.
Burndown, burnup, or both
Configure each gadget to display:
-
A burndown chart showing how remaining work changes over time
-
A burnup chart showing how completed work increases over time
-
A combined view containing both burndown and burnup series
Select only the series that are relevant to your reporting needs.
Flexible data sources
The Sprint Burndown Burnup Chart uses a Scrum board and sprint as its data source. You can select a specific sprint or automatically display the latest or previous sprint.
The Release Burndown Burnup Chart can use:
-
A saved Jira filter
-
A JQL query
-
One or more epics
-
One or more portfolio-level work items, such as initiatives or themes
-
One or more Fix Version values within the selected scope
These options allow you to track releases that span multiple projects, teams, or levels of the Jira work hierarchy.
Flexible measurement options
Calculate progress using:
-
Work Item Count
-
Story Points
-
Original Time Estimate
-
Remaining Time Estimate
-
Time Remaining and Time Spent
-
Other numerical custom fields
This allows teams to measure progress using the estimation method that best matches their planning and delivery practices.
Completed, remaining, and scope series
Display completed work, remaining work, and total scope over time.
The Scope series makes changes to the sprint or release scope visible, helping you distinguish slow delivery from an increase in the amount of planned work.
Completed, remaining, and scope series
Display completed work, remaining work, and total scope over time.
The Scope series makes changes to the sprint or release scope visible, helping you distinguish slow delivery from an increase in the amount of planned work.
Ideal burndown and burnup lines
Compare actual progress against ideal burndown and burnup lines.
The ideal lines can be calculated using the initial scope or current scope. For release reporting, you can also enter a fixed scope value when the total planned work is known but not all corresponding work items have been added to Jira.
Release ETA forecasting
The Release Burndown Burnup Chart can forecast when the remaining work is likely to be completed.
Configure the forecast using:
-
The average velocity from all completed intervals
-
The average velocity from a selected number of recent intervals
-
A fixed velocity entered manually
The chart can display forecast lines for remaining work, completed work, and the estimated release end date.
Scope forecasting
Forecast how the release scope may evolve based on historical scope changes or a fixed scope-change ratio.
The forecasted scope can also be included when calculating the estimated release completion date, helping you account for releases whose scope continues to grow.
Release milestones
Add milestones to evaluate progress at important points in the release timeline.
Milestones can be configured using:
-
Percentages of the release timeline
-
Specific dates
-
Specific dates with custom labels
Past milestones can indicate whether remaining work was above or below the ideal burndown line at that point.
Subtask support
Include subtasks and their estimates in the calculations when they represent meaningful work for your team.
The Sprint Burndown Burnup Chart can be configured to exclude subtasks, include them together with their parent work items, or process only subtasks.
Configurable calculations and display
Customize the displayed series, ideal-line calculation, intervals, colors, legends, key values, gridlines, weekends, and other chart options to match the reporting needs of your team.