Release burndown
Overview
Release Burndown Chart for Scrum team shows burndown based on completed sprints statistics and projected completion dates based on automatically calculated average and manually entered velocity. The Release Burndown Chart is based on one or more releases of the selected Scrum board.
Benefits
Release Burndown Chart answers the following questions:
how much work was completed in release over the last N sprints where N is the configurable option
how much work remains in the release backlog
what are release projected completion dates and number of sprints based on min, average, and max velocity in the last completed sprints
what is the release projected completion date and number of sprints if the velocity of the team is (your value)
what are release velocity and number of sprints if the completion date is (your value)
Key features
available as a report and dashboard gadget
configurable sprints
number of sprints
filter by name
configurable estimation
issue count
story points
time estimate
custom number fields (business value, etc)
configurable forecast
line color
visibility
average line
configurable scope
include/exclude sub-tasks
include/exclude main issues
filter by JQL query
How to configure
The configuration settings are grouped into two categories:
Burndown
Forecast
Burndown settings
Burndown settings affect the part of the burndown chart which displays completed (past) and active sprints.
Title | The name of the Scrum board is displayed on the gadget view as a link to that board in Jira. Using Title option you can define a custom name for the link to the board. This can be useful if you have several gadgets based on the same agile board with different configurations for releases, sprints, issue filters or other gadget parameters. |
Scrum board | Sprints of the selected scrum board will be displayed on the chart. |
Estimation field | Available options are:
When the board is selected the estimation field is set to board's estimation statistics from its configuration. You can change the default value to any other available estimation if needed. |
Time unit | Available when the estimation field is set to Time Estimate. Time values can be displayed in:
|
Releases | Display burndown progress and completion forecast for the issues of the selected releases. |
Parent task | Enable/disable main tasks in the burndown report (enabled by default) |
Sub-task | In all Jira Software reports sub-tasks are not included in velocity, burndown, burndown statistics. Using this option you can include sub-tasks into sprint metrics calculation. |
JQL filter | Filter sprint issues by custom JQL criteria. Using this option you can create a velocity report for any custom Scrum board scope. |
Burndown | Available options:
|
Sprint filter | Quite often sprints of multiple teams are present on the same Scrum board. In that case, you will get the Velocity Chart for sprints of different teams which in most cases is useless. You can filter sprints by name using Sprint filter options to keep only those sprints that match the filter value. Regular expressions can be used as Sprint filter value:
|
Value labels | Annotate all sprint metrics with their number values on the chart. |
Forecast settings
Forecast settings affect the part of the burndown chart which displays projected completion dates and the number of future sprints based on the completed sprints history and/or custom settings and adjustments to automatically calculated forecast. Using this section you can play various what/if scenarios and answer such questions:
what would be the completion date if the velocity is X
what velocity is required if the completion date is X
Forecast targets |  This section contains settings for automatically calculated velocity and complete date. Important option that affects the calculated values is also Sprint count field described below. Every row in the table is displayed in the resulting chart as a line that starts at the end of actualy completed sprints history and the finishes when crossing the remaining work line. |
Sprint count | Min/max/average velocity are calculated based on actual completed sprints. Sprint count defines how many last completed sprints are taken into account when calculating those values. It is recommended to increase this value to at least 7 (default is 3) when the team has enough completed sprints history. |
Sprint length | Sprint length affects calculated completion dates. It is calculated using actual completed sprints, but you can override that value using a manual value. |
Remaining work | Remaining work that you want to calculated the completion dates for is calculated automatically based on the estimated stories in team backlog and all defined future sprints, but you can override that value using a manual value. |