Home
Back
Velocity Formula:
| From: | To: |
Scrum capacity refers to the amount of work a team can complete during a sprint. It's measured in story points and helps teams plan their work effectively based on historical performance and current team availability.
The velocity formula calculates the team's average output per sprint:
Where:
Explanation: Velocity provides a reliable metric for predicting how much work a team can handle in future sprints, enabling better sprint planning and capacity forecasting.
Details: Accurate capacity planning ensures teams don't overcommit or underutilize their resources. It helps maintain sustainable pace, improves predictability, and enables better stakeholder communication about delivery timelines.
Tips: Enter the total story points completed across multiple sprints and the number of sprints measured. Use historical data from 3-5 sprints for more accurate velocity calculations.
Q1: What is a good velocity for a Scrum team?
A: There's no universal "good" velocity - it varies by team size, experience, and project complexity. Focus on consistent velocity rather than absolute numbers.
Q2: How many sprints should I use for velocity calculation?
A: Typically 3-5 sprints provide a reliable average. Too few sprints may not account for variability, while too many may include outdated performance data.
Q3: What factors affect team velocity?
A: Team composition, technical debt, holidays, team member availability, complexity of user stories, and external dependencies can all impact velocity.
Q4: Should velocity be used to compare teams?
A: No, velocity is team-specific and shouldn't be used for comparisons between teams. Different teams use different story point scales and estimation techniques.
Q5: How often should velocity be recalculated?
A: Review velocity after each sprint and recalculate the average regularly, especially when team composition changes or after significant process improvements.