What this Agile Sprint Velocity Calculator does
The Agile Sprint Velocity Calculator turns completed story points and sprint duration into an average delivery rate measured in points per week. Its description is simple: calculate a team's average sprint velocity in story points per week from completed sprint work and sprint duration. This planning estimate assumes the same team and a consistent estimation scale.
Velocity is a record of work a team has completed, expressed using that team's own story-point scale. It can help a project group discuss capacity and compare planning periods. It does not measure individual productivity, quality, customer value, or how difficult another team's work may be. Story points are relative estimates, so a result is meaningful chiefly within a team that estimates consistently.
The calculator asks for two values: Completed story points and Sprint duration (weeks). It divides the first by the second and returns Velocity (points/week), rounded to two decimal places. The weekly unit makes the result easier to interpret when sprint durations differ, though teams may also prefer to plan directly with per-sprint totals.
How to use the Agile Sprint Velocity Calculator
- Enter the total story points the team completed during the period being measured.
- Enter the sprint duration in weeks. Use the elapsed sprint length that corresponds to the completed work.
- Read the result as average completed points per week, rather than as a promise of future output.
For example, suppose a team completed 30 story points during a two-week sprint. Enter 30 for Completed story points and 2 for Sprint duration (weeks). The formula is 30 / 2, so the result is 15.00 points/week. If the team uses two-week sprints, that weekly average corresponds to 30 points across two weeks under the same assumptions.
Use consistent units. A duration of 10 days should not be entered as 10 weeks. Convert the period to weeks first, or choose a whole number of weeks when that matches the actual sprint. The calculator accepts durations from 0.25 to 8 weeks and completed totals from 0 to 1,000 points. These limits keep entries within a practical planning range while allowing short periods and larger totals.
How the Agile Sprint Velocity Calculator formula works
The formula is completed_points / sprint_weeks. It divides completed story points by sprint duration in weeks. Because the denominator is time, the result is a rate: story points per week. The calculation is intentionally direct, so every value in the output can be traced to the two inputs.
For another example, a team that completes 42 points over three weeks calculates 42 / 3 = 14 points per week. A team with 24 points over two weeks calculates 24 / 2 = 12 points per week. The first rate is higher, but that alone does not establish that the first team is more effective. Teams may estimate points differently, work on different kinds of tasks, or face different conditions.
The rate can also be scaled to a planning period by multiplying it by the number of weeks in that period. A team averaging 14 points per week might use that rate to frame discussion about a four-week period. The resulting 56 points is arithmetic based on a steady-rate assumption. It is not a forecast with guaranteed accuracy. The calculator itself reports the weekly rate and does not account for changes in team composition, interruptions, scope, or estimation practices.
Use cases for the Agile Sprint Velocity Calculator
Project planners can use a velocity calculation to summarize a completed sprint or compare several periods for the same team. The number gives a shared starting point for a conversation about upcoming work. It is most useful alongside context about what changed during the period.
- Reviewing a completed sprint: Record the amount of work completed and express it as a weekly average.
- Aligning sprint lengths: Convert totals from different durations into a common weekly unit for discussion.
- Preparing a planning meeting: Bring a recent rate as one input to capacity planning, then consider availability and known work.
- Explaining an estimate: Show how a rate was derived from an observed total and duration rather than presenting an unsupported figure.
For a multi-sprint view, calculate each period with its own completed total and duration. A combined rate across periods can be calculated by dividing the sum of completed points by the sum of the weeks. This weights each period by its duration. Averaging the individual weekly rates equally can produce a different answer when periods have different lengths.
Other factors to consider when calculating velocity
Velocity depends on a team's definition of completed work. Agree on what “done” means and count only work that meets that definition. If partially finished items are included inconsistently, totals across periods become difficult to compare. Keep the point scale stable as well. Re-estimating the same kind of work with a substantially different scale can change the rate even if delivery conditions have not changed.
Team availability also matters. Holidays, support duties, illness, meetings, onboarding, and changing team membership can affect the amount of time available for planned work. The calculator does not adjust for these factors. Note them beside the result so a planning discussion does not treat a lower or higher rate as a complete explanation of performance.
Use the number as a team planning aid, not as an individual target or a quality measure. Pressuring people to increase points can encourage inflated estimates or rushed work. Pair velocity with other relevant information, such as whether work met acceptance criteria and whether important tasks were completed. A single sprint can be unusual, so a series of comparable periods generally gives more context than one calculation.
Finally, remember that story points are not a universal unit. A rate of 15 points per week for one team cannot be reliably converted into another team's expected output. The estimate is most useful when the same group uses similar estimation and completion practices over time.
Frequently asked questions
What does velocity mean in this calculator?
It means completed story points divided by the duration in weeks. The output is an average rate in points per week for the period entered.
Should I include unfinished work?
Use the team's agreed definition of completed work. If an item has not met that definition, leaving it out supports more consistent comparisons between periods.
Can I compare my team's velocity with another team's?
Direct comparisons are usually misleading because story-point scales and estimation habits differ. Use the rate to understand one team's own planning history.
Does this result predict the next sprint?
No. It summarizes the entered period. It can inform a planning conversation, but availability, scope, interruptions, and other conditions may change.
Why is the answer shown per week?
A weekly unit makes rates from periods of different lengths easier to discuss. Multiply the rate by a planning period's weeks only as a simple steady-rate assumption, not as a guarantee.