Team velocity

About this report

The team velocity report shows the man power, LOV (Level of Value) velocity, and LOE (Level of Effort) velocity for teams and their sprints. The report displays in a data table. This report is designed to give a portfolio manager, Scrum Master, team leader, or release train engineer a high-level understanding how much functionality a team delivers in a sprint, given the total team allocation for that sprint.

This report is generated by selecting a target program and PI. 

Use the Extra Configs button at the top-right of the page to filter the list by specific teams.

To navigate to this report:

1. Select Programs in the top navigation bar and select the program you want to view information about.
2. On the sidebar, select Reports in the list of options.
3. Select Team velocity; the report displays.

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; LOE and LOV must be defined for each story, as well as team member allocations.

How are report values calculated? 

• Man Power = total team allocation / 100, rounded off to 2 decimal places; team allocation is a combination of task and defect allocation that was assigned to a user for that team and sprint.
• LOV Velocity = Sum of all Level of Value Points on accepted stories, for the selected team, for each sprint in the selected PI; LOV points are entered for stories via the Story Grid/New Story panel. 
• LOE Velocity = Sum of all Level of Effort Points on accepted stories, for the selected team, for each sprint in the selected PI; LOE points are entered for stories via the Story Grid/New Story panel.

How to interpret this report

It is a common misconception that velocity should continually increase. The sign of a healthy, stable development organization is that velocity remains consistent sprint after sprint for your teams. If LOV and LOE velocities change dramatically from sprint to sprint, this may point to team instability (for example, engaging members in other work continuously) or that work has been estimated inaccurately (whether the stories are too large or estimates are wrong).

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

Use the MP (Man Power) column to compare team velocities when specific man power is allocated; be aware that the team allocation can be made up of full-time workers as well as workers that are only partially allocated.