Velocity

5 minutes 5 Questions

Velocity is a metric used in Agile Release Planning that measures the amount of work a team can complete within a fixed period, typically expressed in story points or hours. Velocity is calculated by tracking the total number of story points or hours completed by the team during each iteration and averaging them over several iterations. This provides a consistent baseline for determining the amount of work the team can handle within a given time frame. Having an accurate understanding of the team's velocity allows for better estimation of release schedules, helps maintain a sustainable pace of development, and promotes continuous improvement as teams strive to increase their velocity over time.

Guide to Velocity in Agile Release Planning

Velocity is a critical concept in Agile project management and directly impacts Agile release planning. It is important because it helps teams estimate how much work they can get done in a given time period, allowing for more accurate planning and forecasting.

Velocity is the measure of the amount of work a team can tackle during a single Sprint and is the key metric in Scrum. Velocity is calculated at the end of the Sprint by totaling the points for all fully completed User Stories.

How it works: Velocity is calculated by averaging the total points of delivered (and accepted) features per iteration over the last few iterations. Higher velocity means the team is able to complete more points (or tasks).

Exam tips: Answering questions on Velocity
1. Understand the definition of Velocity in Agile - the measure of the amount of work a team can take on2. Always remember that Velocity is a metric unique to each team3. Understand how it is calculated - as an average over several iterations4. Know that it facilitates better planning and forecasting5. It's not a reflection of the productivity of the team, but the consistency of the team's work.

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

Question 1

In a 2-week sprint, if a team has a velocity of 40 and wishes to accomplish a 200 point story. How many sprints are required if the velocity remains constant?

3 sprints 5 sprints 6 sprints 4 sprints

Correct Answer: 5 sprints

Given that the team has a constant velocity of 40 points per sprint, it would take them 5 sprints to complete a 200-point story. This is because 200 divided by 40 equals 5. Therefore, the correct answer is '5 sprints'. The rest of the answers are incorrect because their counts do not multiply by 40 to reach 200, which is the total points needed to finish the story.

Question 2

You are the scrum master for Team Bravo. The team's velocity has been stable at 20 points per sprint for the past six sprints. During the past sprint, the team implemented new collaboration tools which resulted in an increase in velocity to 25 points. As a scrum master, how should you approach the velocity for the next sprint?

Assume a new velocity of 25 points going forth as the new standard. Increase the velocity slightly to 22 points as an average of the previous sprints. Change the velocity to 25 points for the next sprint, and revert to 20 points if it doesn't work out. Maintain the historical velocity of 20 points when planning the next sprint and monitor whether the velocity consistently improves over the next few sprints.

Correct Answer: Maintain the historical velocity of 20 points when planning the next sprint and monitor whether the velocity consistently improves over the next few sprints.

Scrum recommends that agile teams take a conservative approach for their velocity, especially after making significant changes. In this case, the team introduced new collaboration tools, which is a significant change. Consequently, the rise to 25 points may still not be consistently achievable in the forthcoming sprints. Therefore, the correct approach is to continue with the historical velocity of 20 points when planning the next sprint and to monitor if the velocity consistently improves over the next few sprints. Jumping straight to a new velocity of 25 could lead to overcommitments, leading to quality issues or unfulfilled commitments. Similarly, arbitrarily adjusting the velocity to an average value or trying out the new velocity for one sprint and reevaluating would lack robustness. It's best to stick with the stable historical velocity and observe the trend over the next few sprints.

Question 3

Your team recently had a sudden drop in velocity, from 40 to 25 points per sprint. What should the team do to analyze and address the decrease in velocity?

Blame one team member and hold them accountable Ask the team to work overtime to make up for lost points. Ignore the drop and continue with the current processes Increase work in progress (WIP) limits to generate faster progress Identify possible factors and discuss potential improvements in the next retrospective Increase sprint duration to recapture the previous velocity

Correct Answer: Identify possible factors and discuss potential improvements in the next retrospective

Addressing a decrease in velocity requires understanding potential issues and taking actions to improve. The best option is to have a discussion with the team in the next retrospective to identify possible factors and decide on improvements. Ignoring or bypassing the problem without a proper analysis may lead to further issues.

Go Premium