Velocity test - Agile Release Planning - Agile Project Management questions

Question 1

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?

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

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.

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. 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. Increase the velocity slightly to 22 points as an average of the previous 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

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?

4 sprints 5 sprints 3 sprints 6 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.

Velocity

Guide to Velocity in Agile Release Planning

Agile Project Management - Velocity Example Questions

Question 1

Question 2

Question 3

🎓 Unlock Premium Access