What this Team Delivery Velocity Calculator does
The Team Delivery Velocity Calculator finds the average number of story points a team completed per workday during a measurement period. Enter the points for work that met your team’s completion criteria and the number of elapsed workdays in that period. The result is an average rate expressed in points per workday.
This is a compact planning measure for reviewing completed work. It does not determine whether the points were estimated consistently, whether the work was valuable, or how long a future project will take. The number is most useful when a team uses the same estimation approach and completion rules across the periods it compares.
The calculator uses two inputs. Completed story points is the sum of the points for eligible work items completed during the observation period. Elapsed workdays is the number of workdays covered by that period. The formula divides the first quantity by the second.
How to use the Team Delivery Velocity Calculator
- Choose a completed period. Use a finished iteration or another clearly defined span of workdays.
- Add completed points. Count only items that satisfied the team’s definition of done within that period. Use the team's existing estimates.
- Enter elapsed workdays. Count the workdays in the period consistently. For example, a five-workday week is entered as 5.
- Read Average Velocity. The result is shown in story points per workday and rounded to two decimal places.
For example, if a team completed 24 points over 5 workdays, the calculation is 24 ÷ 5 = 4.80 points per workday. This describes that observed period. It does not promise that the team will complete 4.80 points on every future workday.
Use whole-number point and workday entries if that matches your tracking practice. The calculator accepts zero completed points, which can accurately describe a period in which no eligible work was completed. The elapsed period must contain at least one workday so that the rate has a valid denominator.
How the Team Delivery Velocity Calculator formula works
The formula is completed story points ÷ elapsed workdays. Its structure is a rate calculation: a quantity of work is divided by the time over which that work was observed. If the inputs are 24 points and 5 workdays, the rate is 4.8 points/workday.
The units matter. Entering points and workdays produces points per workday. If you enter calendar days, hours, or a different work measure, the output no longer represents the stated unit. Keep the period definition and the units consistent whenever you compare results.
This calculation averages across the full period. It does not account for day-by-day variation, holidays, absences, changing team membership, interruptions, work carried over from an earlier period, or changes in estimation. Those influences may affect the observed total, but the calculator has no separate inputs for them. The result should therefore be read as a descriptive average based on the two values supplied.
Story points are relative estimates used by a team. A result in points per workday is not a universal measure that can be compared fairly between unrelated teams. Teams may define a point differently, split work differently, and apply different completion standards. Comparing a team with its own history under a stable method is generally more interpretable than comparing its rate with another group’s.
Use cases for the Team Delivery Velocity Calculator
A project team can use this calculation during a retrospective to summarize a completed period in a consistent format. Recording both the total points and the number of workdays makes the basis of the average visible. Over several periods, the same calculation can help a team discuss whether its observed throughput has been relatively steady or has varied.
It can also support a planning conversation when the team is deciding how much work to consider for a future iteration. In that setting, treat past velocity as context, then account for current capacity, uncertainty, priorities, dependencies, and the team’s judgment. This calculator does not turn a historical average into a reliable delivery commitment or finish-date forecast.
For useful records, keep a short note alongside each result:
- The start and end of the measurement period
- The workday-counting rule used
- The team’s definition of completed work
- Any significant changes in team composition or estimation practice
These notes make a sequence of averages easier to interpret. If the measurement method changes, mark the change rather than assuming that every value belongs to one directly comparable series.
Other factors to consider when calculating velocity
Velocity captures only the relationship between completed points and elapsed workdays. It does not measure product quality, customer outcomes, workload sustainability, or the importance of the work. A higher number by itself does not establish that a team is working better. Estimation is intended to support planning, so changing estimates to raise the metric can make it less useful.
Scope movement also affects interpretation. If work is added, removed, split, or carried over during a period, decide how your team records those items and apply that policy consistently. Include only completed work in the numerator. Work that remains unfinished should not be counted as completed points under the stated definition.
For people and project planning, consider capacity separately. Holidays, part-time schedules, support duties, and planned leave may mean that two periods with the same number of workdays had different available effort. The calculator does not adjust for those conditions. Record them in planning notes and use team knowledge when deciding what amount of work is appropriate to consider.
Finally, avoid treating a single period as a stable baseline. Averages can be affected by unusual work, interruptions, or a small sample. Looking at multiple comparable periods gives more context, while still leaving uncertainty about future work. Keep the measure focused on helping the team plan and learn.
FAQ
What does Average Velocity mean?
It is the completed story points divided by elapsed workdays for the period entered. The displayed unit is points per workday.
Should unfinished work count?
No. The input is for points associated with work that met the team’s completion criteria during the selected period. Apply the same rule each time you calculate the measure.
Can I compare this result with another team’s velocity?
Direct comparison may be misleading because story-point scales, estimation practices, team composition, and definitions of done can differ. The result is more meaningful in the context of one team’s consistent history.
Does this calculator predict a project completion date?
No. It calculates an observed average rate only. A delivery forecast would also require a defined scope, assumptions about future capacity and work, and a way to handle uncertainty and dependencies.
Why must elapsed workdays be at least one?
The formula divides completed points by elapsed workdays. A period with zero workdays would make the rate undefined, so enter a measurement period that covers at least one workday.