What should a Scrum Master convey if a team’s velocity is compared unfavorably to other teams?

When addressing the issue of a team's velocity being compared unfavorably to other teams, it's essential to recognize that each team's velocity is unique and influenced by various factors including team composition, project complexity, and the differing dynamics within teams. Therefore, conveying that context matters is crucial.

Velocity is not merely a number but a reflection of a team's specific circumstances, including their experience, familiarity with the current project, and even the tools they are using. For instance, a newly formed team might have a lower velocity as they are still establishing their working relationships and becoming accustomed to their roles, while a mature team may have optimized their processes and thus show higher velocity.

Focusing on the uniqueness of each team's velocity encourages a culture of improvement rather than competition. It emphasizes that teams should aim to increase their own velocity over time instead of comparing themselves to others. This perspective fosters collaboration, learning, and adaptation — core principles of Agile methodologies.

Moreover, highlighting the importance of context helps teams to understand that velocity should be used as a tool for reflection and continuous improvement rather than a strict metric for performance comparison with others.