Velocity by team (trend)


The old navigation will be removed from Jira Align in early 2024.
Learn more about the upcoming changes

About this report

The Velocity by Team (Trend) report shows the planned velocity versus actual velocity, by Level of Effort (LOE) points, for individual teams participating in a specified program. The report displays the data in the form of a line graph. The LOE point range is on the Y axis, and the sprints on the X axis. You have the option to view data for the last 3, 5, or 10 sprints. 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.

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 program and team. 

To navigate to this report:

If you’re using the new navigation:

  1. Select Teams in the top navigation bar and select the team you want to view information about.
  2. On the sidebar, select Reports in the list of options.
  3. Select Detailed team velocity (trend); the report displays.

If you’re using the old navigation:

  1. Select the Reports icon from the left Navigation menu.
  2. Start typing the report's name in the Search box.
  3. Once found, select the report.
    Note: You can also use the categories on the left to search for the needed reports.


  1. PI must exist in the system and be tied to a program.
  2. Sprints must be created and tied to a PI. 
  3. Teams must be created and tied to a program. 
  4. Stories must be created and tied to a sprint. 
  5. Tasks must be created and tied to stories. 

How are report values calculated? 

  • Planned Velocity: Sum of all effort points from stories assigned to the selected team for each sprint on the report. Stories must be associated with the sprint before the sprint start date for their effort points to be included. 
  • Actual Velocity: Sum of all effort points from accepted stories assigned to the selected team for each sprint on the report. 
  • Average Velocity: Calculated as (Actual Velocity) / (number of sprints displayed on the report)
  • Average High Velocity: Average Velocity + Velocity Range.
  • Average Low Velocity: Average Velocity - Velocity Range.

Note: Velocity Range is set up manually under Administration > Settings > Platform > Team.


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, this shows that your teams may not be stable (for example, you engage members in other work continuously), or that you work estimation is not accurate (for example, stories are too large).

If there are wide fluctuations in the actual velocity, that indicates a poor level of predictability in scope of work that can be expected to be delivered. An ideal team velocity remains steady.

It is also desired that a team becomes more predictable over time. A narrowing of the gap between planned and actual velocity over time is a sign that a team is becoming more mature.

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

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.