What is one method to establish a team’s velocity?
a. Compare The average Story points completed throughout the previous Iterations
b. Add the Story points for all Features completed in the Iteration
c. Add the Story points for all the Stories planned for the iteration
d. Calculate the percentage planned versus actual stories completed during an Iteration.
The Correct Answer and Explanation is :
The correct answer is:
a. Compare the average Story points completed throughout the previous Iterations.
Explanation
Velocity is a fundamental metric in Agile methodology, used to measure the rate at which a team delivers work in a given iteration (Sprint). Establishing a team’s velocity helps forecast future work and aids in sprint planning by providing a realistic capacity estimate.
Why “a” is Correct:
Using the average story points completed across previous iterations is the most reliable method to establish a team’s velocity. This approach ensures that the velocity reflects the team’s historical performance, factoring in variations that naturally occur due to challenges, productivity shifts, or changing priorities. By averaging, you smooth out anomalies like an overly productive or underproductive iteration.
Why Not the Other Options:
- b. Add the Story points for all Features completed in the Iteration:
This approach might give you a snapshot of one iteration but fails to provide an average trend. Teams can have variations in output based on external factors, and relying on a single iteration may lead to unreliable planning. - c. Add the Story points for all the Stories planned for the iteration:
Planned story points do not always equate to completed work. Teams often adjust scope during iterations based on unforeseen challenges, which can make the planned points irrelevant to actual velocity. - d. Calculate the percentage planned versus actual stories completed during an Iteration:
While this measures execution efficiency, it does not directly establish velocity. Percentages don’t convey the absolute volume of work delivered.
Practical Use of Velocity:
By knowing the average velocity, teams can better predict how many story points they can handle in future sprints. This helps align commitments with team capacity, fostering sustainable development and improved stakeholder trust.