---
title: Why is velocity not suitable for comparing different Scrum Teams?
description: "[Velocity](https://www.thescrummaster.co.uk/glossary/velocity/) reflects a [Scrum Team](https://www.thescrummaster.co.uk/glossary/scrum-team/)’s unique dynamics, capabilities, and context, making it a tool for that team's self-assessment and planning. Because each team operates under different conditions, has varying levels of experience, and faces distinct challenges, comparing velocities across teams…"
url: "https://www.thescrummaster.co.uk/docs/why-is-velocity-not-suitable-for-comparing-different-scrum-teams/"
updated: "2024-12-19"
category: Good Practices / Velocity
---

# Why is velocity not suitable for comparing different Scrum Teams?

[Velocity](https://www.thescrummaster.co.uk/glossary/velocity/) reflects a [Scrum Team](https://www.thescrummaster.co.uk/glossary/scrum-team/)’s unique dynamics, capabilities, and context, making it a tool for that team's self-assessment and planning. Because each team operates under different conditions, has varying levels of experience, and faces distinct challenges, comparing velocities across teams is not meaningful or useful.

Additionally, [Velocity](https://www.thescrummaster.co.uk/glossary/velocity/) can be influenced by external factors beyond the [Scrum Team](https://www.thescrummaster.co.uk/glossary/scrum-team/)'s control, such as changes in requirements or dependencies on other teams. These variables make it difficult to predict future performance based solely on past [Velocity](https://www.thescrummaster.co.uk/glossary/velocity/) data. Therefore, [Velocity](https://www.thescrummaster.co.uk/glossary/velocity/) should be used internally within a team rather than as a benchmark for comparing different teams or individual Developers.