Adding Release Prediction Chart to your dashboard
...
Configuring Release Prediction Chart
To set Setting up the Release Prediction Chart is a quick and easy procedure, just fill out the necessary chart configuration fields fields to select what you would like to see on your report:
Fields description
| Field | Description | ||
|---|---|---|---|
SCRUM Board | Choose the SCRUM board for your report. This gives you the flexibility to display what you need on the chart.
| ||
| Start reporting at | Start date for the report. This is a required field. | ||
| Backlog extra issues | The number of issues from the backlog that will be included in the report. The default number of issues is set to 0, which means that the report will process only the tickets that are included into the future sprints and ignore any tickets that are in the backlog. | ||
| Report cumulates | Time metrics for your report, measured in man-days (MD) or story points (SP). | ||
| Deviation lines at | User defined acceptable deviation from the plan, measured in % and can be between 10% and 90%. If you don't want to show view the deviation lines at the moment, just select "(Hide lines)" option from the select dropdown list. The chart will show shows the deviation lines based on the future Sprint estimates and the selected deviation. The selected deviation percent is applied to taken into account when calculating the projected release date and it results the optimistic release date , optimistic, and pessimistic release datedates. You can define what you consider to be a norm as a deviation % from sprints estimates. For example if you set the deviation to 30% and your projected release date is 4/02/2018 and your team is moving faster by 30% than it has been estimated then your release date should be 2/04/2018. If you allow your team to be 30% behind the schedule, your release date will be 5/28/2018. As long as a team is within the deviation norm, the team progress is considered to be on track, and you do not get warnings every time when the actuals line is below the estimates. Everything below the Deviation (late) line is considered to be in danger zone as this means that the work is behind the plan for more than an established deviation normyou can allow for. The danger zone is marked as a transparent red area below the Deviation (late) line. Thus, the main thing is not to let the actuals line get into the danger zone. | ||
| Refresh Interval | The interval at which you want the gadget to be updated updated. |
This is it! When you are done with the setup, click the Save button and a Release Prediction Chart will be displayed.
See also
RPC - Configuring Using Release Prediction Chart