Agile Tools Suite
Velocity Calculator: Story Points Delivered
A simple tool to determine your team’s average velocity based on story points completed in past sprints.
Enter the total story points completed.
Leave blank if the sprint hasn’t happened.
Only include points for fully “Done” stories.
What is Agile Velocity?
In Agile project management, velocity is a key performance indicator that measures the amount of work a development team can complete during a single sprint. This metric is typically expressed in story points, which are units used to estimate the relative effort required to finish a task or user story. The fundamental concept is that the amount of **story points delivered is used to calculate velocity**, providing a data-driven average of the team’s output.
Velocity isn’t about measuring individual performance but rather the collective capacity of the entire team. By tracking it over time, teams can make more accurate forecasts for future sprints, enabling better release planning and stakeholder communication. It serves as a vital tool for understanding a team’s sustainable pace and for identifying trends that might indicate process improvements or impediments.
Velocity Formula and Explanation
The formula to calculate Agile velocity is straightforward: you sum the completed story points over a series of sprints and divide by the number of sprints.
Average Velocity = Total Story Points Completed / Number of Sprints
It is critical to only count story points from user stories that are 100% “Done” by the end of the sprint. Partially completed work should not be included, as this would skew the data and lead to inaccurate forecasts. Typically, an average is taken over the last 3-5 sprints to establish a stable and reliable velocity.
| Variable | Meaning | Unit / Type | Typical Range |
|---|---|---|---|
| Total Story Points Completed | The sum of all story points from fully completed work items across the measured sprints. | Points (unitless number) | Varies (e.g., 50 – 200) |
| Number of Sprints | The count of sprints included in the calculation. | Count (integer) | 3 – 5 |
| Average Velocity | The resulting average number of story points the team can be expected to complete per sprint. | Points per Sprint | Varies (e.g., 15 – 40) |
Practical Examples
Example 1: A Stable Team
A team has just completed its last three sprints. They want to calculate their velocity to plan for the next quarter.
- Inputs: Sprint 1 (28 points), Sprint 2 (30 points), Sprint 3 (29 points)
- Calculation: (28 + 30 + 29) / 3 = 87 / 3 = 29
- Result: The team’s average velocity is 29 points per sprint. They can confidently commit to a similar amount of work in their next sprint planning session.
Example 2: A Team with a Disrupted Sprint
Another team had a sprint affected by a major holiday, resulting in fewer completed points. They need to see how this impacts their average.
- Inputs: Sprint 1 (35 points), Sprint 2 (18 points – holiday sprint), Sprint 3 (33 points)
- Calculation: (35 + 18 + 33) / 3 = 86 / 3 ≈ 28.7
- Result: The team’s average velocity is approximately 28.7 points per sprint. During their retrospective, they should discuss how the average was pulled down by the holiday and decide if they should plan for ~29 points or a higher number for the next sprint, assuming no holidays. For more on this, see our guide on team capacity planning.
How to Use This Velocity Calculator
- Enter Sprint Data: In the input fields provided, enter the total number of story points your team fully completed for each of the past sprints. You should use at least three sprints for a meaningful average.
- Calculate: Click the “Calculate Velocity” button. The tool processes the numbers, ensuring that the **story points delivered is used to calculate velocity** correctly.
- Review the Results: The calculator will display your team’s average velocity, the total points counted, and the number of sprints used in the calculation.
- Analyze the Chart: The bar chart provides a visual representation of the points completed in each sprint against the calculated average. This helps you quickly spot inconsistencies or trends. To better understand these trends, you might want to explore sprint burndown analysis.
Key Factors That Affect Velocity
A team’s velocity is not static and can be influenced by many factors. Understanding these is key to interpreting the metric correctly.
- Team Composition Changes: When new members join or experienced members leave, it can temporarily decrease velocity as the team adjusts.
- Unplanned Work: Urgent bugs or production issues can pull the team away from planned sprint work, reducing the number of story points they can complete.
- Technical Debt: A complex and poorly maintained codebase can slow down development, leading to a gradual decline in velocity.
- External Dependencies: Waiting for other teams or external vendors can create bottlenecks and prevent stories from being completed.
- Sprint Length Consistency: Changing the length of a sprint makes velocity comparisons between them meaningless. A stable cadence is crucial.
- Team Well-being: Burnout, low morale, and holidays all have a direct impact on a team’s productivity and, consequently, its velocity. For better project outcomes, teams can use a sprint commitment calculator to set realistic goals.
Frequently Asked Questions (FAQ)
No. Velocity is a measure of output, not outcome or value. Chasing a higher velocity can lead to poor quality, burnout, and technical debt. The goal is to find a stable, predictable, and sustainable velocity. The focus should always be on delivering value, not just more points.
If a sprint had zero completed points, it should still be included in the calculation (if it was a normal working sprint) as it reflects a real event. It dramatically lowers the average and should trigger a serious discussion in the retrospective to understand what happened and prevent it from recurring.
No. Story points are a relative measure unique to each team. Team A’s “5 points” could be completely different from Team B’s “5 points”. Comparing velocities is a common misuse of the metric and provides no valuable insight.
It’s generally recommended to use the average of the last 3 to 5 sprints. New teams will see more fluctuation, but after a few sprints, a more predictable pattern should emerge.
No, absolutely not. A story is either “Done” or not “Done”. Awarding partial points undermines the accuracy of the metric and can hide issues with breaking down work into small enough pieces.
When team size changes, the old velocity data becomes less relevant. You should continue to track velocity, but expect it to be unstable for a few sprints. It is effectively a “new” team that needs to establish its own velocity baseline.
Velocity is a retrospective measure of what the team *has delivered*. Capacity is a prospective measure of a team’s *availability* for an upcoming sprint (e.g., accounting for holidays and time off). Teams often use their historical velocity to help plan if they have enough capacity for the work they want to commit to. You can learn more about key agile team metrics here.
While some teams track hours, story points are generally preferred because they are a relative measure of complexity, uncertainty, and effort, not just time. This helps avoid debates over how long something “should” take and focuses the conversation on the work’s complexity. You can learn more about cycle time as an alternative metric.
Related Tools and Internal Resources
Improving your team’s processes involves looking at various agile metrics. Here are some related tools and resources that can help:
- Team Capacity Planner: Plan your sprint by taking team availability and holidays into account.
- Sprint Commitment Calculator: Helps teams set realistic sprint goals based on their velocity and capacity.
- Lead Time Analyzer: Measure the total time from when a request is made until it is delivered.
- Sprint Burndown Analysis: Visualize the completion of work throughout the sprint.
- Guide to Agile Team Metrics: A comprehensive overview of the most important KPIs for agile teams.
- Understanding Cycle Time: Learn about another critical flow metric that complements velocity.