Velocity

5 minutes 5 Questions

Velocity is a key metric in Agile EVM. It measures the amount of work a team can tackle during a single Sprint and is the key for determining project timelines. Velocity is calculated at the end of the Sprint by summing up the points for all fully completed User Stories. This concept helps Agile te…

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

Question 1

Given that the team's historical velocity is 40 points per sprint, and the remaining backlog size is 60 points, how many sprints do you anticipate it would take to complete the project?

4 sprints Approximately 2 sprints 5 sprints 6 sprints 1 sprint 3 sprints

Correct Answer: Approximately 2 sprints

Dividing the remaining backlog size by the team's historical velocity provides an estimate for the number of remaining sprints (60 points / 40 points per sprint = 1.5). Round up to approximately 2 sprints.

Question 2

A new member joins your agile team, which has a historically stable velocity. What action should the team consider in the upcoming sprints?

Ask the new member to observe and not contribute during their first sprint Remove some user stories since the new member isn't familiar with the project Decrease the sprint scope due to uncertainty with the new team member Implement mandatory overtime for all team members Increase the sprint scope to account for the new team member's contributions Monitor the team's velocity to identify potential adjustments

Correct Answer: Monitor the team's velocity to identify potential adjustments

It's essential to monitor the team's velocity after bringing in a new team member to identify potential adjustments. The new member's addition should be considered in both the planning and review process. Drastic changes like decreasing scope, removing stories, or enforcing overtime should be avoided without proper analysis.

Question 3

Team Delta, with a well-maintained velocity of 20 points, decides to implement a new tool that may slow them down initially. How should they adjust their velocity for the upcoming sprints?

The team should temporarily suspend the Daily Scrum until the new tool is fully integrated to focus all efforts on mastering the tool. Velocity should be recalibrated based on a theoretical increase in efficiency the new tool promises, projecting higher numbers for forthcoming sprints. The team should expect a potential decrease in velocity as they adapt to the new tool, observing its impact over the next few sprints. The team should adjust their Definition of Done to exclude items that cannot be completed with the new tool until they achieve full proficiency.

Correct Answer: The team should expect a potential decrease in velocity as they adapt to the new tool, observing its impact over the next few sprints.

Velocity is a metric for observing the amount of work a team can complete in a sprint and is used for planning and forecasting purposes. It can fluctuate for various reasons, including the adoption of new tools or changes in team composition. The correct approach is to continue measuring velocity without artificial adjustments, allowing it to naturally reflect the team's current capability. Simply expecting or forcing an unchanged or increased velocity, suspending essential Scrum events, or altering the Definition of Done to fit the tool's current limitations doesn't address the core purpose of velocity or support empirical process control.

🎓 Unlock Premium Access

PMI Agile Certified Practitioner + ALL Certifications

Velocity

Guide to Understanding Velocity in Agile EVM for PMI-ACP Exam

PMI-ACP - Velocity Example Questions

Question 1

Question 2

Question 3

🎓 Unlock Premium Access