Scrum Velocity Calculator
Calculate your team’s velocity to improve sprint planning and forecasting accuracy
Comprehensive Guide: How to Calculate Velocity in Scrum (With Real-World Examples)
Velocity is one of the most important metrics in Scrum, helping teams predict how much work they can complete in future sprints. When calculated and interpreted correctly, velocity becomes a powerful tool for sprint planning, forecasting, and continuous improvement. This comprehensive guide will walk you through everything you need to know about calculating and using velocity in Scrum.
What is Velocity in Scrum?
Velocity in Scrum measures the amount of work a team can complete during a single sprint. It’s typically expressed in story points or other units of measurement that represent the size of user stories. Velocity is not about speed or productivity—it’s about consistency and predictability.
Key Characteristics of Velocity
- Team-specific (cannot compare between teams)
- Used for forecasting, not performance measurement
- Should stabilize over 4-6 sprints
- Affected by team composition and sprint duration
What Velocity Is NOT
- Not a measure of productivity
- Not a target to be increased at all costs
- Not useful for comparing teams
- Not a management KPI
Why Velocity Matters in Scrum
Understanding and tracking velocity provides several important benefits:
- Improved Sprint Planning: Helps teams commit to a realistic amount of work
- Better Forecasting: Enables more accurate release planning and roadmap predictions
- Process Improvement: Identifies trends that may indicate process issues
- Stakeholder Communication: Provides data for transparent discussions about progress
- Team Stability: Helps maintain a sustainable pace of work
| Metric | Without Velocity | With Velocity |
|---|---|---|
| Sprint Planning Accuracy | ±40% variation | ±10% variation |
| Release Forecasting | Wild guesses | Data-driven estimates |
| Team Stress Levels | High (overcommitment) | Balanced (realistic commitments) |
| Stakeholder Trust | Low (unreliable delivery) | High (predictable delivery) |
How to Calculate Velocity in Scrum (Step-by-Step)
Step 1: Complete at Least 3 Sprints
Velocity becomes meaningful after you have data from multiple sprints. We recommend:
- Minimum 3 sprints for initial calculation
- 5-6 sprints for stable velocity
- 10+ sprints for highly reliable forecasting
Step 2: Sum Completed Story Points
For each sprint, add up the story points of all user stories that meet the Definition of Done. Only count:
- Stories fully completed (not “almost done”)
- Stories that meet all acceptance criteria
- Stories that have been demonstrated and accepted
| Sprint | Completed Story Points | Notes |
|---|---|---|
| Sprint 1 | 25 | Team still forming, lower velocity |
| Sprint 2 | 30 | Improved collaboration |
| Sprint 3 | 28 | One team member on vacation |
| Sprint 4 | 32 | Stable velocity emerging |
| Sprint 5 | 34 | Team at full capacity |
Step 3: Calculate Average Velocity
The basic velocity calculation is simple: add up the story points from the last N sprints and divide by N.
Formula:
Average Velocity = (Sum of story points from last N sprints) / N
Example:
(25 + 30 + 28 + 32 + 34) / 5 = 29.8 → Round to 30 story points
Step 4: Consider Additional Factors
For more accurate forecasting, consider these adjustments:
- Team Capacity: Adjust for vacations, training, or other absences
- Story Point Inflation: Account for changes in estimation practices
- Technical Debt: Consider impact of technical debt work
- External Dependencies: Factor in delays from other teams
- Learning Curve: New team members may temporarily reduce velocity
Step 5: Use Velocity for Planning
Once you have a stable velocity, use it to:
- Determine how many story points to commit to in the next sprint
- Forecast when larger features or releases will be completed
- Identify when to add/remove team members
- Set realistic expectations with stakeholders
Advanced Velocity Calculation Techniques
Weighted Average Velocity
Give more weight to recent sprints since they better reflect current team capacity:
Formula:
Weighted Average = (SP₁×1 + SP₂×2 + SP₃×3 + …) / (1+2+3+…)
Example:
(25×1 + 30×2 + 28×3) / (1+2+3) = (25 + 60 + 84) / 6 = 169 / 6 ≈ 28.2
Velocity Range (Confidence Interval)
Instead of using a single number, calculate a range that represents 80% of your historical velocity:
- Sort all historical velocities from lowest to highest
- Remove the bottom 10% and top 10% of values
- Use the remaining range as your velocity confidence interval
Example:
Historical velocities: [22, 25, 28, 30, 30, 32, 34, 35, 38, 40]
Remove bottom 10% (22) and top 10% (40)
Velocity range: 25-38 story points
Normalized Velocity
Adjust velocity for team size changes or sprint duration changes:
Formula for team size changes:
Normalized Velocity = (Current Velocity × Original Team Size) / Current Team Size
Formula for sprint duration changes:
Normalized Velocity = (Current Velocity × Original Duration) / Current Duration
Common Velocity Calculation Mistakes to Avoid
Mistake: Counting Partial Work
Only count story points for work that is 100% complete according to your Definition of Done. Partial credit leads to inflated velocity and unreliable forecasts.
Mistake: Comparing Teams
Velocity is team-specific. Comparing velocities between teams is meaningless because:
- Different teams estimate differently
- Team compositions vary
- Work complexity differs
Mistake: Using Velocity as a Target
Velocity should emerge naturally from the work completed. Artificially inflating velocity by:
- Increasing story point estimates
- Cutting corners on quality
- Working overtime
…will lead to technical debt and burnout.
Real-World Example: Calculating Velocity for a 5-Person Team
Let’s walk through a complete example with a team that has completed 6 sprints:
| Sprint | Duration | Team Size | Completed Story Points | Notes |
|---|---|---|---|---|
| 1 | 2 weeks | 5 | 22 | New team forming |
| 2 | 2 weeks | 5 | 28 | Better collaboration |
| 3 | 2 weeks | 5 | 30 | Stable processes |
| 4 | 2 weeks | 5 | 32 | One team member sick for 3 days |
| 5 | 2 weeks | 5 | 35 | Full capacity |
| 6 | 2 weeks | 5 | 34 | Stable velocity |
Step 1: Calculate Basic Average Velocity
(22 + 28 + 30 + 32 + 35 + 34) / 6 = 181 / 6 ≈ 30.2 story points
Step 2: Calculate Weighted Average (last 3 sprints)
(32×1 + 35×2 + 34×3) / (1+2+3) = (32 + 70 + 102) / 6 = 204 / 6 = 34 story points
Step 3: Determine Velocity Range (80% confidence)
Sorted velocities: [22, 28, 30, 32, 34, 35]
Remove bottom 10% (22) and top 10% (35)
Velocity range: 28-34 story points
Step 4: Plan Next Sprint
Based on this data, the team might:
- Commit to 32 story points (midpoint of range)
- Select stories that sum to 30-34 points
- Consider team capacity (any vacations planned?)
- Review any upcoming complex work that might affect velocity
How to Improve Your Team’s Velocity
While velocity shouldn’t be artificially inflated, there are healthy ways to improve your team’s consistent delivery:
- Reduce Multitasking: Focus on completing stories before starting new ones (limit WIP)
- Improve Estimation: Regularly review and refine your estimation techniques
- Address Technical Debt: Allocate 10-20% of capacity to technical debt each sprint
- Enhance Collaboration: Improve pair programming and code review practices
- Minimize External Dependencies: Reduce blockers from other teams
- Stabilize Team Composition: Maintain consistent team membership
- Improve Definition of Done: Ensure everyone understands what “done” means
- Optimize Sprint Length: Experiment with 1-3 week sprints to find optimal duration
Velocity vs. Other Scrum Metrics
Velocity is just one of several important metrics in Scrum. Here’s how it compares to others:
| Metric | Purpose | How It Relates to Velocity | Frequency |
|---|---|---|---|
| Velocity | Predict future capacity | Primary forecasting tool | Per sprint |
| Cycle Time | Measure work item completion time | Helps identify process bottlenecks that may affect velocity | Continuous |
| Throughput | Count of work items completed | Complements velocity by showing work item volume | Per sprint |
| Sprint Burndown | Track progress within sprint | Helps predict if velocity target will be met | Daily |
| Release Burndown | Track progress toward release | Uses velocity for forecasting completion dates | Per sprint |
| Escaped Defects | Measure quality | High defect rates may indicate velocity is too aggressive | Per release |
Velocity in Different Scrum Variations
1. Standard Scrum
Uses story points and calculates velocity as described above. Most common approach.
2. Kanban with Scrum (Scrumban)
May use cycle time instead of velocity, or combine both metrics for forecasting.
3. SAFe (Scaled Agile Framework)
Uses velocity at the team level, but also introduces:
- Team PI Objectives: Higher-level commitments
- Program Predictability Measure: Tracks if teams meet their PI objectives
- Normalized Story Points: For comparing across teams
4. LeSS (Large-Scale Scrum)
Focuses on feature teams that can deliver end-to-end value. Velocity is:
- Calculated per team
- Used for overall release planning
- Often combined across teams for large initiatives
Academic Research on Velocity in Agile
Several academic studies have examined velocity in agile development:
- Velocity Stability: Research from the Software Engineering Institute at Carnegie Mellon University shows that team velocity typically stabilizes after 4-6 sprints, with variations of ±15% becoming normal.
- Estimation Accuracy: A study published in the IEEE Computer Society journal found that teams using story points for estimation had 30% more accurate velocity predictions than teams using hours.
- Team Size Impact: Research from NIST indicates that velocity per team member decreases in larger teams (8+ members) due to coordination overhead.
Tools for Tracking Velocity
While you can track velocity manually (as shown in our calculator), many agile tools provide velocity tracking:
- Jira: Automatic velocity charts and reports
- Azure DevOps: Velocity widgets and forecasting tools
- Trello (with plugins): Basic velocity tracking
- VersionOne: Advanced analytics and velocity trends
- Targetprocess: Customizable velocity metrics
- Spreadsheets: Simple but effective for manual tracking
Frequently Asked Questions About Scrum Velocity
Q: Should we include bugs in our velocity calculation?
A: It depends on your process. Common approaches:
- If bugs are estimated like stories: Include them
- If bugs are tracked separately: Exclude them
- Best practice: Be consistent in your approach
Q: Our velocity keeps going up. Is this good?
A: Not necessarily. Investigate why:
- Positive reasons: Team improving, better processes
- Negative reasons: Story point inflation, cutting corners
- Action: Review a sample of stories to check estimation consistency
Q: Should we reset velocity when team members change?
A: Generally yes. When team composition changes significantly:
- Note the change in your records
- Consider the new team’s velocity as a new baseline
- Expect 2-3 sprints for the new team to stabilize
Q: How do we handle vacations in velocity calculations?
A: Two common approaches:
- Adjust Capacity: Reduce expected velocity proportionally (e.g., 20% less capacity = 20% less velocity)
- Normalize Later: Track actual velocity and normalize it for full capacity in your records
Q: Can velocity be used to compare teams?
A: No. Velocity is team-specific because:
- Different teams estimate differently
- Work complexity varies between teams
- Team compositions differ
- Comparisons lead to unhealthy competition
Conclusion: Using Velocity Effectively in Scrum
Velocity is a powerful tool when used correctly in Scrum. Remember these key points:
- Velocity is about predictability, not productivity
- It takes 4-6 sprints to establish meaningful velocity
- Velocity should be used for forecasting, not performance measurement
- Team changes (size, composition) affect velocity
- Always consider confidence intervals rather than single numbers
- Combine velocity with other metrics for complete insights
- Transparency about velocity builds trust with stakeholders
By understanding and properly calculating velocity, your Scrum team can make more accurate commitments, improve planning, and deliver value more consistently. Use the calculator at the top of this page to experiment with different scenarios and see how various factors affect your team’s predicted velocity.
For further reading on agile metrics, we recommend these authoritative resources:
- Agile Alliance – Comprehensive guides on agile metrics
- Scrum.org – Official Scrum guides and resources
- Project Management Institute – Research on agile project management