Skip to main content
Special announcement All BVOP™ certification programs are offered with a significant cost reduction. BVOP's mission is to support professionals worldwide. Online Certification Exam
for $ 45
Register now
Get Certified

Team Velocity

Velocity is a measure of work the Team performs during a single Sprint and is measured at Sprints end by calculating the Points of completed User Stories. Knowing velocity, the team can compute an estimate of how long the project will take to complete.

Velocity is a term in Agile product development

Velocity is a term in Agile product development disciplines and is increasingly used today not only by Scrum teams but also by Project Management and Product Management roles.

It's easy to understand the concept, and at the same time, it's а simple idea. Velocity is the "speed" at which teams complete planned tasks.

Velocity needs a fixed period

To be able to measure the "velocity" of a team, some agreed period should be set for active work. This period could be your Sprint.

Calculating Team Velocity

During a Sprint, the entire team completes tasks or User Stories. At the end of the Sprint (a week or two weeks, or any other designated period), the team completed, for example, 10 User Stories (Product Backlog Items).

Each of these 10 tasks, User Stories or Product Backlog items, had specific Story Points. Some Product Backlog item was rated 3 Story Points. Another was rated 8. Some could be 1 or 21.

If we add up the total of these completed 10 items during the Sprint, we get some numbers. For example, 133.

133 is the Velocity value of the team.

What can we use Velocity for?

Planning Sprint work

After we have calculated the Velocity of the team, it can be easier to predict how many tasks or Product Backlog items can be completed by the Development team in the next period (Sprint).

If 133 was the Team Velocity of the past Sprint, the list of planned Product Backlog items (or User Stories) is opened, and the Story Points written for each item are considered.

You start counting the Story Points values ​​of the next waiting and planned items, adding up the Story Points values. When you reach a total points of about 133, you can count on the fact that those planned Product Backlog Items, which have a total of 133 relative time, will be successfully developed by the team during the next Sprint.

Suppose the Development team consists of 5 participants. All these 5 participants together have completed 133 points of work.

If you divide 133 work points into 5 participants, you will receive 26.6. Let's round this number to 27. So we can roughly say that one member of the Development team finishes 27 points in one Sprint.

Business stakeholder and Team Velocity

If a director or business stakeholder asks you to accelerate project work by increasing the size of the team, you may assume the following:

If you add another specialist to the team, the points for the next Sprint, instead of 133, will already be 133 + 27 = 160. Then you can hope that for one sprint, the team will complete 160 points of work. Thus, instead of a total of 10 items, these 160 points may include, for example, 15 items. Your business stakeholders will enjoy faster development.

If one participant leaves the team, you simply subtract 27 from 133 to get 106. The team can produce such work points during the next period (Sprint) if you are left without one participant.

Once you have the team velocity measured in points, you can theoretically calculate an unlimited number of Product Backlog Items in the future and determine how many Sprints (periods, weeks, months, etc.) will be required to complete all items.

Relativity and Velocity

Some important topics to keep in mind about the Velocity:

The further in time you plan, the more inaccurate your estimates will be.

The longer the team works together, the more work (Story) points they can develop over a period.

If you add a new member to the team, keep in mind that the team needs to unite again before you can predict with greater accuracy the Velocity of your team.

If one participant leaves the team, this does not mean that a certain number of points must be subtracted from the total Velocity. This participant may have worked with the largest or smallest capacity.

Everything is relative.

If you change your technology and tools, Velocity will temporarily decline as teams gain substantial experience with new resources and speed up again.

Various factors in a project or organization can affect Velocity's value.

Agile Scrum Velocity Calculation - How to measure and use the velocity of Agile teams?
Comments of our guests
  1. Anita Weber
    Hello. To know exactly and clearly the velocity of the development team after each sprint, I write down what the velocity of the team was during the past sprint. Thanks to these notes, we can predict how many tasks the team can accomplish in the next sprint. Recently, however, the entire team was on vacation because of the end of the year. We have temporarily extended the length of our Scrum sprint from one week to one month. Would you recommend me to ignore the last team velocity of the previous long sprint and watch the velocity of the upcoming regular sprints again? The organization requires an archive with the velocity of the team, and we do averaging of all sprints velocities​​, and that's my problem. The average numbers go weird now.

Web site
Your Comment

The BVOP Certificates

Certified Chief Executive

The BVOP Chief Executive is the core driver of the Business Value-Oriented Principles and the most advanced figure and leads the interest of the organization.

Get Certificate $1290   $720

Certified Program Director

The BVOP Program Director manages the entire Program Management Office and possess exceptional expertise and applies strategies.

Get Certificate $720   $490

Certified Agile Director

The BVOP Director is the most advanced and important role inside Agile products and services-based organizations.

Get Certificate $440   $220

Certified Project Manager

The BVOP Project Manager is an advanced and competent business, product, and technical role and a key factor for the success of the projects.

Get Certificate $280   $130

Certified Product Manager

With the advancing design, development, technical, and business knowledge, the BVOP Product Manager is a master role and decision-maker for the products.

Get Certificate $280   $130

Certified Product Owner

Responsible and skilled BVOP Product Owners balance both business and technical needs using Agile approaches and provide business value for products.

Get Certificate $180   $90

Certified Scrum Master

The BVOP Scrum Master role combines skills, Agile thinking, and project management practices to enchant processes, teams, and stakeholders.

Get Certificate $140   $70

Certified Human Resources Manager

People are the greatest assets of any organization. Balancing the people and organization needs

Get Certificate $140   $70