...
- The time tracking is enabled or the Story Points field is available
- Committed vs Completed report is added is added to your dashboard
- You have configured have configured the Committed vs Completed Gadget
Reading the chart
Your Committed vs Completed Gadget displays the following information:
...
There are the following tabs with the report insights:
Summary tab
Here you can view information about planned and delivered work measured in the selected metrics, average length for the sprint and average velocity, and warnings in case the actual progress is behind the plan. Note: In case source data is not available the panel is hidden.
| Stats | Description |
|---|---|
| Planned sprint length | Sprint length as planned in Jira (start and end dates specified when starting the sprint), measured in weeks. |
| Average sprint length | The actual average duration of a sprint based on when the sprint was actually started and completed. This can be different from what you define as the start / end date for your sprints |
| Average estimate | The average of work committed to be delivered for each sprint in the report. |
| Average accomplished (velocity) | The average of actual work delivered in each sprint, this is your team's velocity. |
| Estimation Error | Percentage of the estimation error for each sprint. Tip: Ensure that you have at least 2 completed sprints to view the Estimation Error line, otherwise it won't be displayed. The estimation error is showing the estimation inaccuracy percentage increase or decrease. For example: Estimation error = (30 - 24) / 24 * 100 = 25% |
| Trend | Estimation accuracy trend:
|
| Average tickets opened | The average number of tickets opened in a sprint. |
| Average tickets closed | The average number of tickets closed in a sprint. |
| Average % of tickets closed | The average percentage of tickets closed in a sprint. |
| Average issue size | The average size of an issue, measured in story points or time depending on which metrics is used. This number is based on the sprints that are selected for the report. |
| Theoretical SP (story point) | Amount of time that one story point equals to for this team, measured in hours. This theoretical value is based on the estimates that the team gives and time it takes to perform work. |
This statistics can help you plan the future sprints. For example you can use average estimated or average accomplished as the value for the ideal team velocity and plan sprints taking this into account.
...
- You have at least 1 completed sprints to filter by the SCRUM board
- You check the Warnings tab from time to time and triage tickets from there. The tickets shown in the Warnings tab are not included into the chart calculations, and thus in order to see the accurate picture on the chart, you might want to triage those tickets first.