Scrum Metrics Explained: Velocity, Cycle Time and Lead Time
Scrum metrics can help a team understand its work, identify patterns and support better forecasting and improvement.
Metrics should support inspection and adaptation, not become targets for judging individual performance.
Why Use Scrum Metrics?
Useful metrics can help answer questions such as:
- How much work are we completing?
- How long does work take?
- Are items getting stuck?
- Is our delivery becoming more predictable?
- Where can we improve our workflow?
1. Velocity
Velocity is commonly used to describe the amount of estimated work completed by a Scrum Team during a Sprint.
For example, if a team completes 30 Story Points that meet the Definition of Done during a Sprint, its velocity for that Sprint may be described as 30 points.
Velocity is a team-specific measure. It should not be used to compare different teams or as a performance target.
Why Can Velocity Change?
Velocity can change because of:
- Different types of work
- Changes in team composition
- Unexpected technical problems
- Changes in understanding
- Different Product Backlog item sizes
A change in velocity is not automatically a problem. The team should look at the context behind the number.
2. Cycle Time
Cycle Time measures how long a work item takes from the defined start point to the defined completion point.
For example:
Completed: 9 September
Cycle Time: 4 days
The exact start and finish points should be clearly defined by the team.
3. Lead Time
Lead Time measures the time from when a request enters the system until it is completed or delivered, depending on how the team defines the measurement.
It can therefore include waiting time before active work begins.
Cycle Time vs Lead Time
4. Throughput
Throughput is the number of work items completed during a specified period.
If a team completes 12 work items in two weeks, its throughput for that period is 12 items.
5. Work in Progress
WIP is the amount of work that has started but has not yet been completed.
High WIP can indicate excessive multitasking, queues or bottlenecks.
Metrics Should Work Together
Looking at only one metric can create a misleading picture.
What Should a Scrum Master Look For?
The Scrum Master should look for trends and questions, rather than isolated numbers.
- Is cycle time increasing?
- Is WIP continuously growing?
- Are items frequently blocked?
- Is throughput changing significantly?
- Are estimates being used responsibly?
What Should NOT Be Done?
Don't ask only "What is the number?"
Ask "What is the number telling us, and what should we inspect?"
Key Takeaway
Metrics are useful when they improve transparency, understanding and decision-making.
No single metric can tell you whether a Scrum Team is successful. Use metrics together with observation, conversation and context.