Scrum team burnup
Overview
Burnup Chart for Scrum team shows burnup based on completed sprints statistics and projected completion dates based on automatically calculated average and manually entered velocity. The Burnup Chart is based on the selected Scrum board.
Benefits
The Burnup Chart answers the following questions:
how much work was completed over the last N sprints where N is the configurable option
how much work remains in the backlog
what are the projected completion dates and number of sprints based on min, average and max velocity in the last completed sprints
what are the projected completion date and number of sprints if the velocity of the team is (your value)
what are the velocity and number of sprints if the completion date is (your value)
How to configure
The configuration settings are split into three categories. Each category is displayed as a separate tab:
Burnup
Issues
Forecast
Burnup settings
Title | The name of the Agile board is displayed on the gadget view as a link to Velocity Chart report of that board. 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 sprints, dates, 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 estimation field is set to Time Estimate. Time values can be displayed in:
|
Burnup | |
Sprint filter | Quite often sprints of multiple teams are present on the same Scrum board. In that case you will get 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 which 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. |
Issues settings
Sub-tasks | In all Jira Software reports sub-tasks are not included into velocity, burnup, burndown statistics. Using this option you can include sub-tasks into sprint metrics calculation. |
Releases | Filter sprint issues by selected releases. Using this option you can create Release velocity report on sprints basis. |
Epics | Filter sprint issues by selected epics. Using this option you can create Epic velocity report on sprints basis. |
JQL filter | Filter sprint issues by custom JQL criteria. Using this option you can create a velocity report for any custom Scrum board scope. |
Forecast settings
Forecast settings affect the part of the burnup 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 and manually defined velocity and complete date. By default the forecast is calculated for min/max/average velocity from the actual history of completed sprints. The most 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. You can change the color using color picker and enable/disable visibility of automatically calculated forecasts using toggle. Custom forecast is defined by color, label and either Velocity or Complete date |
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. |
Remaining work growth | The remaining work often changes over time. To simulate such behavior Remaining work growth can be used. The provided value is the amount of work that you backlog changes in each sprint interval. E.g. you can simulate the situaion when you know that in every sprint your backlog grows for 15 story points etimation unit is defined in Estimation statistics option in the Burnup tab). |
Start date | Start date affects the starting point of of the forecast lines and has two options:
|