VELOCITY

CALCULATION
PROJECT MANAGEMENT
11 / 0 4 / 2 0 2 1
 • Meet the Presenter

• A Definition

• Types of
calculation

Overview • Measurement of
velocity

• Benefits

• Don’ts of velocity
calculation

• End
 VELOCITY IN SCRUM
• Velocity measures the amount of work a development team can do during a sprint.
• It is an indication of the average amount of Product Backlog turned into an
Increment of product during a Sprint by a Scrum Team, tracked by the
Development Team for use within the Scrum Team.
• In Scrum, project work is broken down into user stories, which focus on specific
functionality for an end user. The development team estimates the time and effort
needed to develop and test each user story with points, or a numeric value. The
work completed is the summation of these assigned points for user stories that
have been fully developed and tested.
 TYPES OF VELOCITY CALCULATION IN SCRUM
ACTUAL VELOCITY
Actual velocity is the division of
total number of story points
completed by the number of sprints.
Eg: If the development team has
completed a total of 70 points over
two sprints, the team's actual velocity
would be 35 points per sprint.
EXPECTED VELOCITY
Expected velocity is the division of
total number of estimated story
points by the number of sprints. 
Eg: If the development team
estimates a total of 160 points over
four sprints, the team's expected
velocity would be 40 points per
sprint.
Step 1 

• Calculate the Velocity of the First Sprint.

• Add the points of all user stories delivered by
the development team at the end of the sprint.
This total is called velocity.
MEASURING
Step 2 
VELOCITY
• Use the Velocity to estimate number of sprint
needed.
• Average of all individual sprint velocities is
called average sprint velocity.
BENEFITS OF VELOCITY CALCULATION
 The performance of a development team can be measured.
 Helps to predict how much scope can be delivered by a specific date.
 Helps to predict a date for a fixed amount of scope to be delivered.
 Velocity simplifies sprint planning by allowing you to predict how
many user story points the development team can edit or deliver.
 DON’TS OF VELOCITY CALCULATION

• Never take into account the points of unfinished user stories.

• Never calculate the velocity of individual team members – only do so for the whole
team. Velocity is a team metric.
• Never use the velocity for giving bonuses or other rewards to the team. This will
lead to story point inflation as the team is likely to underestimate their user stories
to achieve higher scores.
Thank You
Adithya Sasi
adiadithya842@gmail.co
m
Phone: 9605508245