A Guide to Velocity in Scrum
Velocity in Scrum refers to the amount of work a team can handle during a single Sprint. This metric is fundamental in Scrum as it lets the team measure their productivity over time, make accurate forecasts for future sprints, and ensure long-term project management success.
Why is it Important?
Velocity is critical in making performance visible and enhancing predictability. It enables the Scrum Team to establish a steady work rhythm and maintain a sustainable pace, reducing the risk of burnout and helping to maintain high levels of quality and productivity.
How It Works?
Velocity is calculated at the end of the Sprint by summing up the Points value of all fully completed User Stories. These points are estimated using the time, complexity, or size of the work. Note that partially completed stories do not count; this ensures that the team focuses on one task to its conclusion before proceeding to the next one.
Exam Tips: Answering Questions on Velocity in Scrum
When tackling exam questions on Velocity in Scrum, remember to:
1. Mention how Velocity is calculated by summing up Points of fully completed User Stories.
2. Highlight its role in establishing a predictable workflow and sustainable pace.
3. Emphasize that Velocity is a metric unique to each team and can differ based on the team's composition, work dynamics, and the complexity of the User Stories.
Also, remember that Velocity is a tool for the Scrum Team’s planning and not a measure of individual productivity or a tool to compare one team with another.