About this report
The Velocity by Team (PI) report shows the actual velocity, in terms of Level of Effort (LOE) points, for individual teams participating in a specified PI. The report displays the data in the form of a data table. The LOE points completed are shown for each team for each sprint in the PI. At the end of the report, an average team velocity is also provided. This report is designed to give a portfolio manager, Scrum Master, team leader, or release train engineer a high-level understanding of whether a team is on track and completing consistent amounts of work.
It is beneficial to review the report with team members during pre- and post-PI meetings, general team meetings, and during sprint review meetings. This report is generated by selecting a target PI.
- Select the Reports icon from the left Navigation menu.
- Start typing the report's name in the Search box.
- Once found, select the report.
Note: You can also use the categories on the left to search for the needed reports.
- PI must exist in the system and be tied to a program.
- Sprints must be created and tied to a PI.
- Teams must be created and tied to a program.
- Stories must be created and tied to a sprint.
- Tasks must be created and tied to stories.
How are report values calculated?
- Velocity = Sum of all Level of Effort Points on accepted stories, for the selected team, for each sprint in the PI. LOE points are assigned to individual stories via the Story panel.
- Average Team Velocity = Sum of all LOE points divided by count of team sprints.
- Teams listed in the report are teams that are tied to programs that are participating in the PI.
When the PI contains a set of synced sprints across all teams, the report displays multiple columns, each representing a common sprint. Teams are displayed as rows. Within the PI's Details slide-out panel, the Schedule Type field must be set to Synchronized Sprints.
When the PI contains independent sprints, a single column is displayed for velocity. Each row represents a unique team and sprint combination.
How to interpret this report
It is a common misconception that you want velocity to continually increase. The sign of a healthy, stable organization and team is that velocity remains steady. If you see many peaks and valleys in the LOE totals, this shows that you do not keep your teams stable (for example, you engage members in other work continuously), or that you do not estimate your work well (whether the stories are too large or estimates are wrong). Wide fluctuations indicate a poor level of predictability in scope of work that can be expected to be delivered.
Join the Atlassian Community!
The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.
Need to contact Jira Align Support? Please open a support request.