Velocity in Scrum

5 minutes 5 Questions

Velocity is a metric used in Scrum for predicting how much work a team can complete in a sprint. It is calculated by adding the estimates of the work completed in the previous sprints. This provides the team with an understanding of their capacity and helps them in planning effectively for future s…

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.

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

CSM - Velocity in Scrum Example Questions

Test your knowledge of Velocity in Scrum

Question 1

The velocity of your Scrum team is inconsistent across sprints making planning and forecasting difficult. How should you address this?

Use the highest velocity achieved by the team as a benchmark for all future sprints to ensure consistency in sprint planning. Automatically adjust the velocity based on the average of the last three sprints to smooth out any inconsistencies. Collaborate with the team to review the sprint retrospectives to identify any patterns or recurring issues that may be causing the variability in velocity. Implement a more rigorous estimation technique, such as T-Shirt sizing, to ensure all team members have a consistent understanding of the effort involved, thereby reducing variability in velocity. This may involve a comprehensive retraining on estimation techniques and the adoption of new tools to support the improved process, potentially realigning the team’s understanding of work complexity and effort estimation.

Correct Answer: Collaborate with the team to review the sprint retrospectives to identify any patterns or recurring issues that may be causing the variability in velocity.

Velocity is a metric that should be used for the team by the team to aid in forecasting. It's important to understand the reasons behind velocity fluctuations rather than attempting to artificially standardize or manipulate it. Discouraging the team from improving or altering estimates to fit a perceived consistency can stifle agility and improvement. The correct answer encourages open communication and reflection on past sprints to naturally improve the estimation process and remove impediments, aligning with Scrum principles of transparency, inspection, and adaptation.

Question 2

Your Scrum team's velocity has remained the same, while other teams' velocities have increased. The Product owner is raising concerns. As a Scrum Master, how would you respond?

Encourage the Product Owner to focus on the team's delivery of value rather than comparing velocities. Recommend the team adopts additional Agile methodologies to boost their velocity. Suggest implementing more rigorous daily Scrum meetings to directly address the velocity issue. Advocate for the introduction of performance-based incentives for the team, aligning directly with increases in their velocity, thereby motivating them to enhance their performance metrics.

Correct Answer: Encourage the Product Owner to focus on the team's delivery of value rather than comparing velocities.

Velocity is an internal metric used by Scrum teams to measure their own performance and progress over time. It is not designed as a comparative tool between teams, as each team's composition, working style, and challenges are unique. The correct response emphasizes improving value delivery over numerical comparison, aligning with Agile and Scrum values. Suggesting more rigorous daily Scrums, adopting additional methodologies, or introducing performance incentives might seem like viable strategies but could lead to misunderstanding Agile principles, unnecessary pressure, and a shift away from focusing on delivering value.

Question 3

A Scrum team is consistently delivering complete PBIs, however, the velocity seems to always be lagging. As a Scrum Master, how would you handle the situation?

Encourage the developers to pair program on complex tasks to decrease the time taken, thus possibly increasing the velocity. Though it may foster learning and collaboration, it doesn't directly address velocity calculation or estimation issues. Review the accuracy of effort estimation and ensure backlog items are adequately refined. Adjust the definition of done to include fewer criteria, making it easier to complete PBIs. Introduce a buffer sprint where the team focuses on tasks that were underestimated in previous sprints.

Correct Answer: Review the accuracy of effort estimation and ensure backlog items are adequately refined.

The correct approach involves reviewing how effort estimation is conducted to tackle the problem of lagging velocity in a more systemic way. By refining backlog items more accurately, the team can have a better understanding of the work involved and thus forecast their velocity more effectively. Adjusting the definition of done could undermine the quality of the work delivered and does not address estimation accuracy. Introducing a buffer sprint does not solve the root of the estimation issue; it's more of a temporary workaround. Pair programming might enhance work quality and team skills but does not directly influence the accuracy of velocity measurement or the root causes of estimation issues. The key is to ensure effort estimations are realistic and reflect the team's capacity.

🎓 Unlock Premium Access

Certified ScrumMaster + ALL Certifications

🎓 Access to ALL Certifications: Study for any certification on our platform with one subscription
3861 Superior-grade Certified ScrumMaster practice questions
Unlimited practice tests across all certifications
Detailed explanations for every question
CSM: 5 full exams plus all other certification exams
100% Satisfaction Guaranteed: Full refund if unsatisfied
Risk-Free: 7-day free trial with all premium features!

Start Your Free 7-Day Trial