Sprint Velocity Calculator
Calculate your Scrum team's velocity to improve sprint planning and forecasting. Track completed story points across sprints to determine your team's average velocity and predict future sprint capacity.
| Sprint | Story Points Completed | Sprint Length (Days) | Notes | |
|---|---|---|---|---|
Velocity Metrics
Total Sprints: 4
Total Story Points: 0
Average Velocity: 0.0 points/sprint
Velocity per Day: 0.0 points/day
Min Velocity: 0 points
Max Velocity: 0 points
Sprint Forecasting
Estimated Sprints: 0.0 sprints
Conservative Estimate: 0.0 sprints
Create a board to help you manage your projects
What is Sprint Velocity?
Sprint Velocity is an Agile metric that measures the amount of work a Scrum team can complete within a specific time frame, typically a single sprint. It's expressed in story points and helps teams plan future sprints more accurately.
The Velocity Formula:
Velocity = Total Story Points Completed ÷ Number of Sprints
Key Principles:
- Only Completed Work Counts: Only user stories that meet the Definition of Done count toward velocity
- Team-Specific Metric: Velocity is unique to each team and shouldn't be compared across teams
- Historical Data: Use 3-5 recent sprints for the most accurate velocity calculation
- Planning Tool: Velocity helps predict how much work can be completed in future sprints
How to Use This Velocity Calculator
- Enter your sprint name (e.g., "Sprint 1", "Q1 Sprint 3")
- Story Points: Input the total story points completed in each sprint
- Sprint Length: Enter the duration of each sprint in days
- Notes: Add context like team changes, holidays, or impediments
- The calculator automatically computes your team's average velocity
- Use the forecasting section to estimate how many sprints needed for future work
Best Practices for Velocity Tracking:
- Track velocity consistently across multiple sprints (minimum 3-5)
- Only count fully completed user stories that meet acceptance criteria
- Include notes about factors that affected velocity (team changes, impediments, etc.)
- Use velocity for planning, not performance evaluation
- Remember that velocity may fluctuate and typically stabilizes over time
- New teams often start at 5-10 story points per person per 2-week sprint
Understanding Velocity Variations:
- Higher Velocity: May indicate improved team collaboration, better understanding of work, or simpler tasks
- Lower Velocity: Could be due to complex work, team changes, external dependencies, or impediments
- Consistent Velocity: Shows team maturity and predictable delivery capability
Using Velocity for Planning:
- Use average velocity to plan sprint capacity
- Consider using conservative estimates (lower end of velocity range) for important deadlines
- Account for upcoming holidays, team changes, or known impediments
- Review and adjust velocity calculations quarterly or after significant team changes
Create a board to help you manage your projects