Back to Scrum Metrics

Velocity

5 minutes 5 Questions

Velocity is a metric that predicts how much work Scrum Team can complete during a sprint. It's calculated at the end of the sprint by summing up the Points for all fully completed User Stories. Velocity is used for planning purposes and is unique to each team. Since the way of estimating tasks can differ from one team to another, comparing velocity metrics across different squads might not give the expected insights. For velocity to become useful, the team's composition, work patterns, and estimation manner should remain consistent over time, and it will make their Velocity predictable and a reliable forecast tool.

Guide to Understanding Velocity in Scrum

Velocity is a vital part of the Scrum framework and is widely used in Agile project management.

Why is it important?
Velocity provides an estimation of the amount of work a Scrum team can handle during a single Sprint and helps in future planning and effective distribution of tasks.

What is Velocity?
Velocity in Scrum refers to the amount of work a team can tackle during a single Sprint, usually measured in story points or hours. It is calculated at the end of each Sprint by summing up the points for all fully completed User Stories.

How does Velocity work?
Velocity is calculated over time and gives an average of work done in previous Sprints. This average represents the team's Velocity. It helps the team estimate how much work they can commit to in a future Sprint.

Exam Tips: Answering Questions on Velocity
1) Understand the basic concept of Velocity and how it's calculated.
2) Be aware that Velocity is a measure of a team's capacity and not their performance.
3) Knowledge of Velocity aids in managing stakeholder expectations and in planning future Sprints.
4) Remember, Velocity varies from team to team and even Sprint to Sprint for the same team. Comparisons should not be drawn based on Velocity.
5) Velocity is not a key performance indicator or a metric to predict the team's productivity. It is primarily a planning tool.

Test mode:
Start practice test
PSM I - Scrum Metrics Example Questions

Test your knowledge of Amazon Simple Storage Service (S3)

Question 1

Team Omega uses a standardized velocity calculation method based on their past sprints. Which formula best represents the most reliable way to calculate velocity?

Correct Answer: Average of the completed story points from the last 3-5 sprints

The most reliable method to calculate velocity is using the average of completed story points from the last 3-5 sprints. This approach provides: 1. Historical data that reflects actual team performance 2. Recent enough timeframe to be relevant 3. Sufficient sample size to account for variations 4. Focus on actual completed work rather than predictions Other options are problematic because: - Including anticipated points from technical improvements adds speculation to velocity calculations - Using all historical sprints could include outdated data not reflecting current team capability - Adding arbitrary buffers (like 20%) distorts real performance metrics - Using only the last sprint's median is too narrow and doesn't account for sprint-to-sprint variations - Multiplying by team capacity percentage adds unnecessary complexity

Question 2

In calculating team velocity for newly formed teams that have highly variable story point completion rates, which approach is most effective?

Correct Answer: Use the median of completed story points from the first three sprints

Using the median of completed story points from the first three sprints is the most effective approach for new teams with variable velocity for several reasons: Strengths of this approach: - The median is more resistant to outliers than the mean - Three sprints provide enough data to see patterns while staying recent - It accounts for the team's actual performance during their forming stage - Provides a realistic baseline for future planning Why other approaches are less effective: - Using averages with confidence factors can be too arbitrary and may not reflect team reality - Dividing by team members assumes equal productivity and fails to account for team synergy - Using mode with percentage additions introduces unnecessary complexity and may not represent true capacity The median approach provides the most stable and realistic velocity metric during the team's early stages, while avoiding the impact of extreme variations that are common with new teams.

Question 3

During sprint planning, two team members express different opinions about a user story's complexity and give it different story point estimates. How should the team resolve the discrepancy?

Correct Answer: Conduct a collaborative discussion to reach a consensus

Collaborative discussion is the best method for resolving discrepancies in story point estimation. The team should discuss the factors contributing to each estimate, and come to a shared understanding and consensus on the user story complexity. Using arbitrary decisions or unilaterally choosing one estimate can lead to inaccuracies in the team's velocity.

Go Premium

Professional Scrum Master I Preparation Package (2024)

  • 2149 Superior-grade Professional Scrum Master I practice questions.
  • Accelerated Mastery: Deep dive into critical topics to fast-track your mastery.
  • Unlock Effortless PSM I preparation: 5 full exams.
  • 100% Satisfaction Guaranteed: Full refund with no questions if unsatisfied.
  • Bonus: If you upgrade now you get upgraded access to all courses
  • Risk-Free Decision: Start with a 7-day free trial - get premium features at no cost!
More Velocity questions
37 questions (total)
Start 37 question test