Use Team Metrics to review how much work the Team completed during the planning interval (PI).
- Seeing how much work was completed.
- Finding the regular capacity.
Who Should Review Team Metrics?
Team metrics should be reviewed by all Team members.
Reviewing Team Metrics
- Navigate to the Team Metrics folder.
- Expand Teams, then Team Metrics.
- Select the desired view within the Team Metrics folder.
- Descriptions of each view are found in the next section of this article.
- Use the Team filter to show the appropriate Team, if not already selected.
Understanding Team Metrics Reports
Cumulative Flow
What does it measure?
The Cumulative Flow diagram shows how many User Stories and Bugs are in each State at any given time within the last 90 days, represented by the vertical distance between curves. It also captures the rate at which User Stories and Bugs are accepted into a working state (arrival curve) and the rate at which User Stories and Bugs are completed (departure curve). This diagram can be used to visualize bottlenecks that need to be addressed to enable faster flow of value.
Why is it important?
Having too much work in progress (WIP) causes Teams to be overloaded, priorities to be misunderstood, and context switching to occur, all of which result in increased Flow Time and decreased Flow Velocity. Because of this, WIP needs to be measured and subsequently limited to improve the flow of value.
Team Velocity
What does it measure?
Note: This data will populate only for Teams that assign Effort (Story Points) and Team Iterations to Stories and Bugs.
The Team Velocity chart shows the amount of Effort Completed for each Team Iteration in the current and immediately preceding PI. It also shows the average amount of Effort Completed across those Team Iterations, which can be used to help determine the Capacity (input as Velocity in Targetprocess) for future Team Iterations.
Why is it important?
Past velocity can be a good gauge for future capacity, which is critical for roadmapping. However, significant variation in velocity decreases the ability to accurately forecast into the future. Although the application of agile principles and practices can help to increase velocity over time, a constant increase in velocity is not typically sustainable, so maintaining a steady velocity is desirable.
Team Burn-Up
What does it measure?
Note: This data will populate only for Teams that assign Effort (Story Points) and Team Iterations to Stories and Bugs.
- The Team Burn-Up: Current Iteration chart shows the number of Story Points (Effort) completed over time for the current Team Iteration.
- The Team Burn-Up: Previous Iteration chart shows the number of Story Points (Effort) completed over time for the immediately preceding Team Iteration.
Why is it important?
The Team Burn-Up shows if and how the team is incrementally delivering against the Stories and Bugs within the Team Iteration. If the team is not incrementally delivering, the chart will show more as a flat line for large portions of the Team Iteration, which could be an indicator of too much WIP, bottlenecks, or other waste in the system.