Velocity

Introduction

Velocity is one of the most commonly used Agile metrics in Scrum. It measures the amount of work a Scrum Team completes during a Sprint.

Velocity helps Scrum Teams:

• Understand team capacity
• Improve Sprint Planning
• Forecast future delivery
• Track team performance trends
• Support release planning

Velocity is typically measured in Story Points, though some teams may use other units like User Stories or ideal hours.

Understanding Velocity properly is essential for effective Agile planning, forecasting, and continuous improvement.

What is Velocity?

Velocity is the total number of Story Points (or other estimation units) completed by a Scrum Team during a single Sprint.

Only work that meets the Definition of Done is counted toward Velocity.

Incomplete or partially done work is NOT included in Velocity.

Purpose of Velocity

Velocity helps Scrum Teams:

• Measure team throughput
• Improve Sprint Planning accuracy
• Forecast delivery timelines
• Track performance consistency
• Identify improvement opportunities
• Support realistic commitment decisions

Why Velocity is Important in Agile

Without Velocity data:

• Sprint Planning may be unrealistic
• Teams may overcommit or undercommit
• Release forecasting becomes difficult
• Performance trends are invisible
• Improvement progress cannot be tracked

Velocity provides data-driven insights for better Agile planning and decision-making.

How Velocity is Calculated

Velocity is calculated by adding the Story Points of all completed User Stories during a Sprint.

Example

User Story	Story Points	Status
User Login	3	Done ✅
Password Reset	5	Done ✅
Payment Integration	8	Done ✅
Order Tracking	5	Not Done ❌

Sprint Velocity:

3 + 5 + 8 = 16 Story Points

The incomplete "Order Tracking" story is NOT counted.

Average Velocity Calculation

Scrum Teams typically use average velocity from multiple Sprints for better forecasting accuracy.

Example

Sprint	Velocity
Sprint 1	20
Sprint 2	24
Sprint 3	22
Sprint 4	26

Average Velocity:

(20 + 24 + 22 + 26) ÷ 4 = 23 Story Points per Sprint

This average helps plan future Sprint capacity.

Velocity Range

Instead of using only average velocity, many teams use a velocity range for more realistic planning.

Example

• Lowest Velocity: 20 Story Points
• Highest Velocity: 26 Story Points
• Average Velocity: 23 Story Points

The team may plan future Sprints within the range of 20–26 Story Points.

How Velocity is Used in Scrum

1. Sprint Planning

Velocity helps the team decide how many Story Points to select for the Sprint Backlog.

Example

If average velocity is 23 Story Points, the team selects approximately 23 points of work.

2. Release Planning

Velocity helps forecast release timelines.

Example

• Remaining Product Backlog: 92 Story Points
• Average Velocity: 23 Story Points per Sprint
• Estimated Sprints to Release: 92 ÷ 23 = 4 Sprints

3. Capacity Adjustment

If team availability changes (leaves, holidays), velocity expectations are adjusted accordingly.

4. Performance Trend Tracking

Velocity trends over multiple Sprints help identify:

• Improving performance
• Declining productivity
• Inconsistent delivery
• Impact of process changes

Velocity Trends

Stable Velocity

Velocity remains consistent across Sprints.

Indicates:

• Predictable delivery
• Effective planning
• Stable team

Increasing Velocity

Velocity gradually increases over time.

May indicate:

• Improved processes
• Better estimation
• Growing team skills

However, sudden large increases should be investigated as they may indicate:

• Estimation inflation
• Quality reduction

Decreasing Velocity

Velocity drops over time.

May indicate:

• Technical debt impact
• Team morale issues
• Increased complexity
• Team member changes

Highly Variable Velocity

Velocity fluctuates significantly between Sprints.

May indicate:

• Unstable requirements
• Poor estimation practices
• External interruptions
• Inconsistent team availability

Velocity Chart

A Velocity Chart is a visual representation of Sprint velocities over time.

Typical Velocity Chart Structure

Axis	Description
X-Axis (Horizontal)	Sprint numbers or dates
Y-Axis (Vertical)	Story Points completed

Velocity charts typically show:

• Committed Story Points
• Completed Story Points
• Average Velocity line

Velocity and Estimation

Velocity depends on estimation consistency.

If estimation practices change frequently:

• Velocity data becomes unreliable
• Planning accuracy decreases
• Forecasting becomes difficult

Teams should maintain consistent estimation standards for reliable velocity tracking.

Role of Scrum Master in Velocity Management

The Scrum Master helps by:

• Tracking velocity trends
• Facilitating Sprint Planning using velocity data
• Encouraging realistic commitments
• Identifying performance issues
• Supporting continuous improvement
• Protecting velocity from misuse

Role of Product Owner in Velocity

The Product Owner uses velocity to:

• Forecast release timelines
• Prioritize Product Backlog
• Set realistic stakeholder expectations
• Plan product roadmap

Role of Developers in Velocity

Developers contribute by:

• Estimating User Stories consistently
• Completing work to Definition of Done
• Improving development practices
• Providing realistic capacity information

Benefits of Velocity

Benefit	Description
Improved Sprint Planning	More realistic work selection
Better Forecasting	Data-driven release predictions
Performance Visibility	Tracks team throughput trends
Reduced Overcommitment	Helps maintain sustainable pace
Improved Predictability	Consistent delivery expectations
Supports Continuous Improvement	Identifies improvement opportunities

Velocity vs Other Agile Metrics

Metric	Focus
Velocity	Work completed per Sprint
Burndown Chart	Remaining work during Sprint
Burnup Chart	Work completed over time
Lead Time	Time from request to delivery
Cycle Time	Time from work start to completion
Throughput	Number of items completed per time period

Velocity Anti-Patterns

Velocity should NOT be used for:

Anti-Pattern	Problem
Comparing teams	Different teams estimate differently
Employee evaluation	Velocity is a team metric, not individual
Performance pressure	Leads to estimation inflation
Velocity as target	Focuses on numbers instead of value
Ignoring quality	Rushing work to increase velocity

Common Challenges in Velocity Tracking

Challenge	Description
Inconsistent Estimation	Changing estimation standards
Team Composition Changes	New or departing members affect velocity
External Interruptions	Support work reduces available capacity
Estimation Inflation	Inflating points to appear productive
Incomplete Work Counting	Counting partially done stories

Best Practices for Velocity Management

• Count only fully completed stories
• Maintain consistent estimation practices
• Use average velocity for planning
• Track velocity trends over time
• Adjust for team availability changes
• Use velocity as planning tool, not performance target
• Focus on value delivery alongside velocity

Common Mistakes in Velocity Usage

• Comparing velocities between different teams
• Using velocity for individual performance evaluation
• Counting incomplete work in velocity
• Pressuring teams to increase velocity
• Ignoring quality to increase numbers
• Treating velocity as fixed number

Velocity and Sustainable Pace

Agile promotes sustainable pace, meaning:

• Teams should not be pressured to continuously increase velocity
• Consistent velocity is more valuable than high velocity
• Quality should never be sacrificed for higher velocity
• Team wellbeing is more important than velocity numbers

Real-Life Example

Example:

A Scrum Team developing an online food delivery application tracks velocity over 6 Sprints:

Sprint	Velocity
Sprint 1	18
Sprint 2	22
Sprint 3	20
Sprint 4	24
Sprint 5	22
Sprint 6	26

Average Velocity: (18 + 22 + 20 + 24 + 22 + 26) ÷ 6 = 22 Story Points

Remaining Product Backlog: 88 Story Points

Estimated Sprints to Release: 88 ÷ 22 = 4 Sprints

The Product Owner uses this data to communicate realistic delivery expectations to stakeholders.

Importance of Velocity in Agile

Velocity is important because it:

• Supports data-driven planning
• Improves Sprint predictability
• Enables release forecasting
• Helps identify performance trends
• Supports continuous improvement

Conclusion

Velocity is a fundamental Agile metric that helps Scrum Teams measure throughput, improve Sprint Planning, forecast delivery timelines, and track performance trends over time.

When used responsibly as a planning tool — not as a performance pressure mechanism — Velocity helps Agile teams maintain sustainable pace, improve predictability, deliver consistent value, and achieve long-term Agile success.