Velocity

5 minutes 5 Questions

Velocity is a fundamental metric in agile methodologies that measures the amount of work a team can complete during a single sprint. It is calculated by summing the story points of all fully completed user stories at the end of a sprint. Velocity provides teams with empirical data to forecast future work and plan sprints more effectively. By analyzing velocity trends over multiple sprints, teams can assess their performance, make necessary adjustments, and improve predictability. It helps in setting realistic expectations with stakeholders by providing insights into how much work the team can handle. Additionally, velocity aids in identifying issues like overcommitment or underperformance. For instance, a consistently declining velocity might indicate impediments or inefficiencies that need to be addressed. Conversely, a stable or improving velocity suggests that the team is becoming more efficient. It's important to note that velocity is a relative measure and should not be used to compare different teams, as it can lead to unhealthy competition and undermine collaboration. Instead, it should be used internally by a team to drive continuous improvement. Understanding velocity helps a Disciplined Agile Scrum Master facilitate better sprint planning sessions, manage stakeholder expectations, and guide the team towards achieving sustainable pace and delivering value consistently.

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

Question 1

When using velocity as a planning metric, what is most critical to ensure its effectiveness?

Adjusting story point values upward each sprint to reflect team improvements and learning curves Maintaining consistent story point estimation techniques across sprints Comparing the team's velocity with other teams to establish organizational benchmarks Calculating velocity based on the highest performing sprint to set ambitious targets

Correct Answer: Maintaining consistent story point estimation techniques across sprints

Maintaining consistent story point estimation techniques across sprints is crucial for velocity to be an effective planning metric. Consistency in estimation allows teams to: - Make meaningful sprint-to-sprint comparisons - Establish reliable forecasting patterns - Build trust in their planning process - Create predictable delivery expectations The other options are problematic because: Adjusting points upward each sprint artificially inflates velocity and breaks the consistency needed for reliable measurement. Comparing velocities between teams is not valuable since each team estimates differently and works on different types of work. Basing targets on highest performing sprints creates unrealistic expectations and encourages gaming the metric rather than focusing on sustainable delivery patterns.

Question 2

In analyzing velocity patterns, what indicates the most reliable measure of a team's capability?

The highest achieved velocity across multiple sprints multiplied by a standard deviation factor The median velocity over several sprints that accounts for both peaks and troughs The average velocity from the last three sprints adjusted for team composition changes The mathematical mean of all historical sprint velocities normalized against team size

Correct Answer: The median velocity over several sprints that accounts for both peaks and troughs

The median velocity over several sprints is the most reliable measure because: Key reasons for using median velocity: - It provides a balanced view by naturally filtering outliers - Accounts for both high-performing and challenging sprints - Represents actual sustainable team performance - Less affected by temporary anomalies Why other approaches are less effective: - Using highest velocity with standard deviation is overly optimistic and may set unrealistic expectations - Looking at only the last three sprints provides too narrow a sample size and may be skewed by recent events - Mathematical mean can be significantly distorted by outliers or unusual sprint performances The median provides the most stable and realistic representation of team capacity, making it the most reliable metric for future planning and commitment purposes.

Question 3

What aspect of velocity measurement makes it most useful for agile team planning?

It establishes a guaranteed minimum output level that teams must achieve each sprint It enables teams to calculate exact delivery dates for all future project milestones It represents actual team capacity based on real performance data It provides a precise measurement system to evaluate individual team member contributions

Correct Answer: It represents actual team capacity based on real performance data

Velocity measurement is most valuable because it represents actual team capacity based on real performance data from past sprints. This historical data provides reliable insights for future planning. Here's why the other options are incorrect: Establishing a guaranteed minimum output contradicts agile principles as velocity naturally fluctuates and should not be used as a rigid performance target. Velocity is a team metric, not meant to evaluate individual contributions, as this would harm team collaboration and shared responsibility. While velocity helps with forecasting, it cannot provide exact delivery dates due to the inherent variability in software development and changing circumstances that affect team performance.

Go Premium

Disciplined Agile Scrum Master Preparation Package (2024)

Velocity

DASM - Metrics and Measuring Success Example Questions

Question 1

Question 2

Question 3

Go Premium