Velocity
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 teams to understand how much they can deliver in a time-frame and helps to forecast future work delivery.
Guide to Understanding Velocity in Agile EVM for PMI-ACP Exam
What is Velocity?
Velocity measures the quantity of work a team completes during a single iteration or sprint. It is usually measured in story points or hours and acts as a predicting tool for the planning of future sprints.
Why is Velocity Important?
Understanding velocity is key to manage the project's progress and scope. It helps teams predict their performance over time, making it possible to adjust plans and expectations related to project timelines.
How Does Velocity work in Agile EVM?
Velocity is the rate at which the project team completes work. It is calculated by tallying completed user stories' points in each sprint. In Agile EVM, Velocity can be used to estimate project completion by comparing it to the backlog.
Exam Tips: Answering Questions on Velocity
Understanding Velocity is essential for the PMI-ACP exam. Here are some tips:
- Remember that velocity is a measure of work completed in a given iteration, not a measure of individual performance.
- Velocity should not be used to compare different teams. It's a tool for self-assessment and project planning.
- Fluctuations in velocity can signal issues or changes within the team.
- Questions may ask you to calculate velocity, make sure you understand the formula: Velocity = Total of Completed Estimated Story/Feature Points / Number of Iterations.
PMI-ACP - Velocity Example Questions
Test your knowledge of Velocity
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?
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?
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?