# Sprint Metrics Check

By analyzing the metrics (velocity chart or cumulative flow diagram) of a sprint, the agile team gets the chance to reflect about their development speed, about whether or not to have achieved their initial sprint goal and how they can do better in the future, starting with the next sprint.

# Subject

Inspect and Adapt / Retrospective

# Motivation

The retrospectives are the best sessions at the end of a sprint to inspect and adapt a team's behavior and work. Teams then reflect and identify improvement backlog items via a structured, problem-solving way. As a consequence, the team's performance and motivation is expected to continuously increase.

# Procedure

The Agile Master prints or draws the team's velocity chart from the last sprint. It has to be made visible, what initial amount of work was planned and which part of it was achieved by the end of the sprint. In addition, one can also print or draw the last sprint's cumulative flow diagram, where it is visible which amount of work is still in progress, which amount was finished, which amount is still open, which amount is blocked. These categories can be personalized for each team (using the tool Jira Atlassian). Depending on the team's sprint results, the Agile Master writes down the following questions on the flipchart or whiteboard: Why did we not achieve the amount of work we committed to during the last planning? What could be the main reasons? What can we do to become more successfully regarding our sprint goals?

# Facilitator

Agile coach/agile master

# Participants

The entire agile team

# Results

Information about the progress.

# Tools

Whiteboard/flipchart, sticky notes

# See also

Atlassian Jira - Velocity chart, Cumulative Flow Diagram