10X: Velocity by Team (Trend)

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. 


Prerequisites

  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 Level of Effort Points on stories assigned to the selected team for each sprint on the report. LOE points are entered for stories via the story grid or a new story panel.
  • Actual Velocity = Sum of all Level of Effort Points on accepted stories, for the selected team, for each sprint on the report. LOE points are entered for stories via the story grid or a new story panel.
  • Average Velocity = Sum (Actual Velocity of every sprint for the selected period) / Count of sprints.
  • 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.

Velocity_by_Team_Trend.png

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.