Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your existing Jira Software Cloud site to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Create powerful rules to start automating your manual, repetitive processes.
This page is for company-managed projects
If the lower-left of your project sidebar says you're in a team-managed project, check out these team-managed project articles instead.
Learn more about the difference between company-managed and team-managed projects.
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 you can feasibly commit to.
Viewing the Velocity Chart
Click Projects in the navigation bar and select the relevant project.
Click Reports then select Velocity Chart.
The Velocity Chart will be displayed, showing your last seven completed sprints.
Understanding the Velocity Chart
Estimation statistic: The y-axis displays the statistic used for estimating stories. In the example above, the team is using story points. Estimates can also be based on business value, hours, issue count, or any numeric field of your choice. See Configuring estimation and tracking for more info.
Commitment: The gray bar for each sprint shows the total estimate of all issues in the sprint when it begins. After the sprint has started, any stories added to the sprint, or any changes made to estimates, will not be included in this total.
Completed: The green bar in each sprint shows the total completed estimates when the sprint ends. Any scope changes made after the sprint started are included in this total.
Sprints: The x-axis displays the last 7 sprints completed by the team. This data is used to calculate velocity.
Other things to note about the Velocity Chart:
It's board-specific, which means it'll only include issues that match your board's saved filter.
It's based on your board's column mapping. An issue is considered to be 'To Do' when it is in a status that has been mapped to the left-most column of your board. Similarly, an issue is considered to be 'Done' when it is in a status that has been mapped to the right-most column of your board. See Configuring columns for more information.
A team's recent velocity can be useful in helping to predict how much work can be completed by the team in a future sprint. Velocity is calculated by taking the average of the total completed estimates over the last several sprints. So in the chart above, the team's velocity is (17.5 + 13.5 + 38.5 + 18 + 33 + 28) / 6 = 24.75 (we've ignored the zero story point sprint). This means that the team can be expected to complete around 24.75 story points worth of work in the next sprint.
This value should become more accurate and reliable over time, as more data becomes available and the team gets better at estimating issues.
Estimates from sub-tasks are not included in the Velocity Chart's calculation. (Only estimates from parent tasks are included.)
Need help? If you can't find the answer you need in our documentation, we have other resources available to help you. See Getting help.
Was this helpful?