Team Benchmarks

Cross-team comparison for learning, not ranking

Velocity (story points)

Platform62pts

Mobile45pts

Data38pts

Frontend54pts

Cycle Time (days)

lower is better

Platform3.2d

Mobile4.8d

Data2.1d

Frontend2.8d

PR Review Time (hours)

lower is better

Platform6h

Mobile12h

Data4h

Frontend5h

Deployments / Week

Platform4/wk

Mobile2/wk

Data6/wk

Frontend5/wk

DevEx Score

Platform78

Mobile65

Data72

Frontend81

All Teams — Benchmark Data

Team benchmark data comparing velocity, cycle time, PR review time, deployments per week, and DevEx score
Team	Velocity	Cycle Time	PR Review	Deploys/wk	DevEx
Platform	★ 62 pts	3.2 d	6 h	4	78
Mobile	45 pts	4.8 d	12 h	2	65
Data	38 pts	★ 2.1 d	★ 4 h	★ 6	72
Frontend	54 pts	2.8 d	5 h	5	★ 81

★ = best in class. Green values = best in class. Lower is better for Cycle Time and PR Review.

Team Benchmarks provide performance comparison data across teams. The purpose is learning, not competition — a team with lower velocity but higher code quality and fewer incidents may be healthier than a team shipping fast with high failure rates. Use benchmarks to start conversations about what's working and identify where teams can learn from each other.

Retrospective

Share one benchmark comparison per retro. Ask: 'Data team deploys 6x/week while Mobile deploys 2x — what can we learn from their process?' Avoid framing as 'Mobile needs to catch up.'

Leadership review

Present benchmarks alongside context. High velocity with high cycle time may mean large batches — not necessarily a problem, but worth understanding.

Cross-team sync

Use benchmarks to identify mentoring opportunities. A team excelling in PR review time can share their approach with teams where reviews are a bottleneck.

Relevant endpoints: team_metrics and company_metrics.