What is Velocity in Scrum Methodology?
Velocity is a is a capacity planning tool that represent how much work load a Scrum Team can successfully complete within a two-week sprint (or similar time-boxed period).
Velocity is a useful tool to estimate how impetuous and efficient the Scrum Team can complete the issues. The value is calculated by reviewing the Scrum Team’s successfully completed items in previous sprints.
This value will be guide to estimate the coming sprints and Project termination times.
Formula is very simple;
Velocity = Number of completed story points / One iteration
In velocity formula the term “completed” is the key point. Therefore, deliverables are the main matric to calculate the Velocity. Regarding to that, getting the accurate matric, Grooming the issues under one day long is a key point. If there is an issue on your backlog with 2-day long story point and it is half done; in the velocity calculation, team’s day long work is not counted.
As known, in Scrum, number of item (task) is not an indicator to measure the effort. That is why, story points should be used for velocity calculation and this used to monitor the Scrum Team’s efficiency not for the individual team member’s velocity.
In some platforms, Velocity Graph provides to monitor “Average Velocity”, “Best Velocity”, “Worst Velocity” to reflect the capacity of the team. As known, human is the key sources of projects. I strongly suggest my colleagues to take
s notes if the sprints velocity is either lower or higher than the average one. There might be an input for the Sprint Retrospective Meeting which would guide you to improve the velocity and productivity.
In conclusion, Scrum framework is a whole form with its terms, phrases and aspects. Velocity is one of the components of this wholeness. This metric reflects the limits and flexibility of the team in terms of work load to expand awareness about capabilities of the team and plan the future sprint.
You can also find my last 3 articles about Scrum Methodology from the links below;