Velocity

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.

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.

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.