Velocity-Based Planning
Velocity-Based Planning
Introduction
Velocity-Based Planning is an Agile planning technique where Scrum Teams use historical velocity data to forecast how much work can be completed in future Sprints.
Velocity helps teams make realistic Sprint commitments and improve delivery predictability by using actual past performance instead of assumptions.
Velocity-Based Planning is widely used in Scrum for:
- Sprint Planning
- Release Planning
- Capacity Forecasting
- Roadmap Estimation
What is Velocity?
Velocity is the amount of work completed by a Scrum Team during a Sprint.
Velocity is usually measured using:
- Story Points
- User Stories
- Work items completed
In Scrum, Story Points are the most common measurement unit.
What is Velocity-Based Planning?
Velocity-Based Planning is the process of using previous Sprint velocity data to estimate how much work the team can complete in upcoming Sprints.
It helps teams:
- Make realistic Sprint commitments
- Improve Sprint predictability
- Avoid overcommitment
- Forecast release timelines
Purpose of Velocity-Based Planning
Velocity-Based Planning helps Scrum Teams:
- Improve Sprint Planning accuracy
- Predict future delivery capacity
- Support realistic workload management
- Improve Agile forecasting
- Increase delivery reliability
How Velocity is Calculated
Velocity is calculated by adding the Story Points of completed User Stories during a Sprint.
Example
| User Story | Story Points |
|---|---|
| User Login | 3 |
| Password Reset | 5 |
| Payment Integration | 8 |
Total Completed Story Points:
3 + 5 + 8 = 16 Velocity
Average Velocity Calculation
Scrum Teams often calculate average velocity using multiple previous Sprints.
Example
| Sprint | Velocity |
|---|---|
| Sprint 1 | 20 |
| Sprint 2 | 24 |
| Sprint 3 | 22 |
Average Velocity:
(20 + 24 + 22) ÷ 3 = 22 Story Points
The team may use:
- 22 Story Points as future Sprint capacity estimate
How Velocity-Based Planning Works
Step 1: Review Historical Velocity
The team reviews completed Story Points from previous Sprints.
Step 2: Calculate Average Velocity
Average velocity is determined using recent Sprint data.
Step 3: Adjust for Capacity Changes
The team adjusts estimates for:
- Vacations
- Holidays
- Team size changes
- Support activities
Step 4: Select Sprint Work
The team selects Product Backlog items matching estimated velocity capacity.
Step 5: Finalize Sprint Commitment
Sprint Backlog and Sprint Goal are finalized.
Velocity-Based Planning Example
Average Team Velocity:
- 30 Story Points per Sprint
Upcoming Sprint Conditions:
- One Developer on leave
- Public holiday during Sprint
Adjusted Planning:
- Commit to 24–26 Story Points instead of 30
This helps maintain realistic Sprint commitments.
Velocity-Based Planning vs Capacity Planning
| Aspect | Velocity-Based Planning | Capacity Planning |
|---|---|---|
| Focus | Historical performance | Current availability |
| Measurement | Story Points completed | Hours or availability |
| Purpose | Forecast future delivery | Determine available working capacity |
| Data Source | Past Sprint results | Current Sprint conditions |
Velocity Trends
Velocity trends help teams understand:
- Delivery consistency
- Improvement over time
- Planning stability
- Potential process problems
Stable Velocity
Indicates predictable delivery.
Highly Variable Velocity
May indicate:
- Unstable requirements
- Poor estimation
- Team disruptions
- Technical challenges
Benefits of Velocity-Based Planning
| Benefit | Description |
|---|---|
| Improved Predictability | Better Sprint forecasting |
| Realistic Sprint Commitments | Reduces overcommitment |
| Better Release Planning | Supports delivery forecasting |
| Improved Team Confidence | More achievable Sprint goals |
| Supports Agile Planning | Improves Sprint and roadmap planning |
| Data-Driven Decisions | Uses actual team performance data |
Role of Product Owner in Velocity-Based Planning
The Product Owner:
- Prioritizes Product Backlog items
- Supports realistic Sprint scope selection
- Aligns Sprint work with business priorities
Role of Developers in Velocity-Based Planning
Developers:
- Estimate User Stories
- Review previous Sprint performance
- Select achievable Sprint work
- Provide technical complexity input
Role of Scrum Master in Velocity-Based Planning
The Scrum Master:
- Facilitates Sprint Planning
- Supports realistic commitments
- Helps analyze velocity trends
- Encourages continuous improvement
Velocity-Based Release Planning
Velocity can help estimate release timelines.
Example
Remaining Product Backlog:
- 120 Story Points
Average Team Velocity:
- 30 Story Points per Sprint
Estimated Release Timeline:
120 ÷ 30 = 4 Sprints
Common Challenges in Velocity-Based Planning
| Challenge | Description |
|---|---|
| Inconsistent Velocity | Highly variable Sprint performance |
| Poor Estimation | Inaccurate Story Point estimates |
| Team Changes | Changing team composition affects velocity |
| External Interruptions | Support work impacts delivery |
| Overreliance on Velocity | Ignoring other planning factors |
Best Practices for Effective Velocity-Based Planning
- Use multiple Sprint averages
- Adjust for team availability changes
- Keep Story Point estimation consistent
- Focus on sustainable pace
- Review velocity trends regularly
- Use velocity as guidance, not strict target
Common Mistakes in Velocity Usage
- Comparing velocities between teams
- Using velocity as employee performance metric
- Ignoring Sprint capacity changes
- Overcommitting based on best Sprint only
- Treating velocity as fixed value
Velocity Anti-Patterns
Velocity should NOT be used for:
- Employee evaluation
- Team competition
- Management pressure
- Artificial velocity inflation
Velocity is a planning tool, not a productivity ranking system.
Real-Life Example
Example:
A Scrum Team developing a food delivery application has:
- Average Velocity → 35 Story Points
For the next Sprint:
- One Developer is on leave
- Production support activities are expected
The team adjusts Sprint commitment to:
- 28 Story Points
This helps maintain realistic Sprint expectations and improves Sprint success probability.
Importance of Velocity-Based Planning in Agile
Velocity-Based Planning is important because it:
- Supports realistic Agile forecasting
- Improves Sprint planning accuracy
- Encourages sustainable delivery pace
- Reduces overcommitment risk
- Improves product delivery predictability
Conclusion
Velocity-Based Planning is a powerful Agile planning approach that uses historical team performance to forecast future Sprint capacity and delivery expectations.
By using velocity responsibly, Scrum Teams can improve planning accuracy, Sprint predictability, release forecasting, and sustainable Agile delivery success.