Team Velocity Calculator
Calculate your agile team's velocity by dividing completed story points by sprint duration in weeks. Use this metric for sprint planning, capacity forecasting, and estimating when a product backlog will be delivered.
About this calculator
Team velocity is an agile metric that measures how much work a team completes in a given time period, expressed as story points per week. The formula is Velocity = Story Points Completed / Sprint Duration (weeks). Story points are relative estimates of effort, complexity, and uncertainty assigned to backlog items. Sprint Duration is the length of the sprint, typically 1–4 weeks. Velocity is not a measure of productivity in the traditional sense — it is a planning tool. Once a team's average velocity is established over several sprints, it can be used to forecast how many sprints are needed to complete a backlog: Sprints Needed = Total Backlog Points / Average Velocity. Consistent velocity over time indicates a stable, predictable team, while significant variation may signal scope issues, team changes, or estimation drift.
How to use
Suppose your team completed 42 story points during a 2-week sprint (Sprint Duration = 2 weeks, Story Points Completed = 42). Apply the formula: Velocity = 42 / 2 = 21 story points per week. If your product backlog contains 210 remaining story points, you can estimate the work remaining: 210 / 21 = 10 weeks, or roughly 5 more two-week sprints. This helps the product owner set realistic release dates and decide which features to prioritize in the backlog.
Frequently asked questions
How many sprints of data do I need to calculate a reliable team velocity?
Most agile practitioners recommend using at least 3 to 5 completed sprints before relying on velocity for planning purposes. Early sprints often show higher variability as the team calibrates its estimation and working rhythms. After 5 or more sprints, you can calculate an average velocity and use a rolling average of the most recent 3 sprints to account for team changes or process improvements. A single sprint's velocity should never be used in isolation for long-range forecasting, as it may not reflect the team's sustainable pace.
Why does team velocity differ between sprints even when the team size stays the same?
Velocity naturally varies between sprints due to factors such as public holidays, team member absences, the complexity mix of stories in that sprint, technical debt, and interruptions from unplanned work. Story point estimation also introduces subjectivity — a story estimated at 5 points by one team member may feel like 8 points to another. Over time, teams tend to stabilize their estimation patterns, reducing velocity variance. Rather than chasing a single target number, healthy agile teams focus on maintaining a sustainable pace and continuously refining their estimation accuracy through retrospectives.
What is the difference between team velocity and team capacity in agile planning?
Team velocity is a historical measurement of how many story points a team actually completed per sprint, based on past performance. Team capacity is a forward-looking estimate of available hours or effort for an upcoming sprint, accounting for holidays, part-time availability, and planned absences. Velocity is used to forecast long-range delivery timelines, while capacity is used to set the sprint commitment for the next sprint. Both are important: capacity helps you decide how many points to pull into a sprint, while velocity provides the baseline for that decision and helps validate whether your commitment is realistic.