$ luamere benchmarks --sources=shown
Is this good?
The numbers we use to read a team's delivery, and where they come from. Benchmarks are a starting point: the trend of your own team matters more than any single figure.
// shipping speed and stability
From commit to production.
| measure | top teams | typical / low | source |
|---|---|---|---|
| Lead time for changes (commit to production) | under 1 day | 1 day to 1 week (high), up to 1 month (medium), 1-6 months (low) | DORA 2024 performance clusters |
| Change failure rate (changes that need a fix or rollback) | about 5% | up to about 40% (low performers) | DORA 2024 performance clusters |
| Pull request cycle time (first commit to production) | under 25 hours | about 7 days on average; 4 of them in review | LinearB 2026 benchmarks (8.1M PRs, 4,800 teams) |
// code review
Where work quietly waits.
| measure | guide | why | source |
|---|---|---|---|
| Time to first review | within 1 working day | "One business day is the maximum time it should take to respond to a code review request." | Google engineering practices |
| Pull request size | a few hundred changed lines at most | Reviewers find fewer defects beyond about 400 lines at a time. | SmartBear study at Cisco (2,500 reviews) |
| Time a PR waits before its first review | under 30% of the time it is open | Above that, review is the bottleneck, not coding. | Luamere guide |
// free: a copy-paste config that labels review time and flags large PRs
// sprints and flow
Do plans hold?
There are no solid public benchmarks for these, so these are the guide values we use in a Delivery Health Check, read together with the team's own trend.
| measure | on track | at risk | off track |
|---|---|---|---|
| Commitment reliability (planned work finished) | 80%+ | 60-80% | under 60% |
| Carry-over (items moved to the next sprint) | under 15% | 15-30% | over 30% |
| Unplanned work (added mid-sprint) | under 20% | 20-35% | over 35% |
| Work in progress per person | 1-2 items | 3 | 4+ |
| Blocked items | under 5% | 5-15% | over 15% |
| Hotfixes and rollbacks per release | under 10% | 10-40% | over 40% |
// guide values: Luamere Delivery Health Check. Not a law of nature: a team at 70% that keeps improving is in better shape than one stuck at 82%.
// your numbers
Where does your team stand?
Two minutes: the free self-check. One week: your real numbers from your own tracker in a Delivery Health Check.