Track the amount of work completed from sprint to sprint. This helps you determine your team’s velocity and estimate the work your team can realistically achieve in future sprints.
| Sprint | Commitment | Completed | Delta | Rolling 5 Sprint Avg Velocity |
| Sprint 1 | 24 | 16 | -8 | — |
| Sprint 2 | 16 | 0 | -16 | — |
| Sprint 3 | 27 | 16 | -11 | — |
| Sprint 4 | 23 | 31 | +8 | — |
| Sprint 5 | 26 | 18 | -8 | 16.2 |
| Sprint 6 | 26 | 43 | +17 | 21.6 |
| Sprint 7 | 23 | 39 | +16 | 29.4 |
Benefits of a Velocity Chart
The Velocity Chart shows the amount of value delivered in each sprint, enabling you to predict the amount of work the team can get done in future sprints. It is useful during your Sprint Planning meetings, to help you decide how much work your team can feasibly commit to.
When to Use a Velocity Chart
The Velocity Chart should be updated at the end of each sprint and used as an input to your Sprint Planning meetings to help your team decide how many story points from the Product Backlog to take into the next sprint based on Average Velocity and comitted vs completed trends.
Calculating Rolling 5 Sprint Average Velocity
The Rolling 5 Sprint Average Velocity for a team can be calculated by taking the mean of the last 5 sprints. In the above example, the Rolling 5 Sprint Average Velocity for the example team is 29.4 story points per sprint with an upward velocity trend. (16 + 31 + 18 + 43 + 39) / 5 = 29.4. In this example, the team can use the average velocity of 29.4 as a guide for the amount of story points to take in next sprint.
Enhanced Velocity Charts using EazyBI for Jira
Using eazyBI for Jira, you can create more detailed Velocity Charts that automatically calculate the Rolling 5 Sprint Average velocity and identify sprint items that were added, removed, committed and not completed. You can also drill through the data in the charts and dynamically slice the data by different dimensions.