Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects 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.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
This page is for team-managed projects
If the lower-left of your project sidebar says you're in a company-managed project, check out these company-managed project articles instead.
Learn more about the difference between company-managed and team-managed projects.
The Velocity report shows how much work was delivered in each sprint. This helps you predict the amount of work your team can do in future sprints. It's useful during your sprint planning meetings, to help you decide how much work you can feasibly commit to.
Before you begin
In team-managed projects, the Velocity report can only be used if you have the Sprints feature enabled. Learn more about sprints.
What is velocity?
Velocity is the average amount of work a scrum team completes during a sprint. In team-managed Jira Software projects, this can be measured in either story points or number of issues.
Teams can use velocity to predict how quickly they can work through the backlog because the report tracks the forecasted and completed work over several sprints. The more sprints, the more accurate the forecast.
How to read the report
The vertical axis displays the statistic used for estimating stories. The horizontal axis displays the last 7 sprints completed by the team; this data is used to calculate velocity.
The Commitment (blue) 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.
The Completed (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.
Things to keep in mind
If the Estimation feature has been enabled, your report will display using your team's story point estimates for each issue.
If Estimation hasn't been enabled, your report will display using the number of issues, which means they will treat each issue as having equal weighting.
The report does not use data from subtasks, even if your project's subtasks have their own estimates. The report will only use data from standard-level issue types like Stories, Bugs, or Tasks.
Was this helpful?