Comparison metrics for agile teams
Metrics should create equal ground, not a leaderboard. Four comparison metrics that motivate agile teams without punishing them.

Comparing agile teams is difficult, and it is worth asking why we compare them at all. How does comparing teams in different domains actually help?
Creating a competition
Teams should not be ranked against each other on arbitrary metrics. That only demotivates people. Instead, metrics should give every team an equal opportunity to compete. Performance then improves because teams want it to, not because someone is pushing.

Create a competition
The metrics for creating equal opportunities
Here are four basic metrics for comparing teams. They measure each team's ability to compete on equal ground, nothing more. Comparable metrics create equal opportunities.
Successful sprints
If a sprint were only a time frame, it would serve no purpose. A sprint is a milestone and needs a goal. The sprint goal (the most important set of stories) is the larger milestone; completing every story is the smaller one. Hold a cross-team demo at the end of each sprint where teams present what they delivered. That healthy competition encourages teams to finish their sprint goals. People need a visible goal to be motivated.

Sprint to a goal
Could this turn into a game of over- and under-commitment? If a team under-commits, the demo makes it obvious: there is less to show. If it over-commits, the demo becomes yet another failed sprint. Delivering what the team committed to builds the motivation to do more. Teams feel satisfied with the work.
Velocity stability and the honest estimation
This is knowledge work, not assembly-line work. If nobody on the team understands a problem well enough to estimate its solution, the problem was not researched in advance.
A time-boxed spike in the previous sprint, followed by a team review of the findings, makes it easy to split the implementation into smaller stories and estimate them properly. For complex work, write a fuller technical design document that lists the implementation stories.
The spike and the design work are themselves stories that can be estimated. The key is defining the structure and sequence of work for a complex solution. Instead of committing to a story the team does not understand, create a research task to fill the gap. Then estimation is grounded in evidence.
Capacity predictability (avoiding unexpected work)
Research comes first; implementation follows. As research uncovers problems, new tickets are created and estimated. You then have a much clearer picture of the next sprint. Known work can be estimated and planned; unknown work gets a time-boxed research ticket before it is estimated. The discipline is splitting large work into small, estimable pieces.
Complex work can start early, even if only to discover that it needs its own set of stories. That still reduces the risk of the unknown.
Support and production firefighting usually run in a time-boxed Kanban flow outside the sprint. There, time to first response and SLA breaches become the comparison metrics.
Team availability (time spent on tasks divided by total time in a sprint)
Availability is the share of time team members spend on estimated work. If one team is pulled into training, knowledge sharing or other internal work more often than others, fix the imbalance. The only way to keep velocity stable is to keep availability stable. When availability between teams is equal, the other comparison metrics will work.
Comparing teams is not about punishing low performance, but about increasing motivation and the spirit to compete and deliver more. That is why those metrics should not be visible to individual team members: they are a tool for coaching, not for public rankings. By tracking these metrics and guiding Scrum Masters indirectly, you give teams equal footing to compete.
Related articles
- Managing sprint dependencies with chained pull requestsDependent tickets stall a sprint while people wait. Learn how stacked pull requests keep work moving and reduce idle time.
- Sheepherding story pointsOpen votes let the first estimate anchor the room. See how the sheep effect skews story points and how to run planning poker honestly.
- The 10% Scrumban rule for every sprintCommitting to full capacity makes every sprint fragile. A 10% Scrumban buffer absorbs risk, protects the sprint goal and lets velocity grow naturally.
About AELBOX
AELBOX is the team behind Scrumpy Planning Poker for Jira. We write about agile estimation, sprint planning and delivery.