Metrics Community Benchmarks
Updated 14 hours ago
Metrics Community Benchmarks
The LinearB Engineering Metrics Benchmarks were created from a study of 1,542 dev teams. For the first time since DORA published their research in 2014, engineering teams are able to benchmark their performance against data-backed industry standards. Continue reading to learn more about our data collection and metric calculations here.
We define 4 categories of quality:
Elite | Strong | Fair | Needs Improvement | |
Cycle Time | Average: < 55 hours 75th %: < 42 hours | Average: 55-102 75th %: 42-95 | Average: 102-180 75th %: 95-188 | Average: 180+ 75th %: 180+ |
Coding Time | Average: < 14 hours 75th %: < .5 hours | Average: 14-25 75th %: .5-1 | Average: 25-46 75th %: 1-4.5 | Average: 46+ 75th %: 4.5+ |
Pickup Time | Average: < 6 hours 75th %: < 1 hour | Average: 6-12 75th %: 1-3 | Average: 12-20 75th %: 3-14 | Average: 20+ 75th %: 14+ |
Review Time | Average: < 8 hours 75th %: < 1 hour | Average: 8-18 75th %: 1-5 | Average: 18-34 75th %: 5-21 | Average: 34+ 75th %: 21+ |
Deploy Time | Average: < 4 hours 75th %: < 1 hour | Average: 4-51 75th %: 1-20 | Average: 51-168 75th %: 20-196 | Average: 168+ 75th %: 196+ |
PR Size (number of code changes | Average: < 235 lines 75th %: < 105 lines | Average: 235-380 75th %: 105-155 | Average: 380-710 75th %: 155-229 | Average: 710+ 75th %: 229+ |
Rework Rate | Average: < 8% 75th %: < 2% | Average: 8-11% 75th %: 2-6% | Average: 11-13% 75th %: 6-12% | Average: 13+ 75th %: 12+ |
What is the difference between average and 75th percentile?
Measuring your organization's cycle time from the 75th percentile is LinearB's recommendation for the most effective method of finding a balanced representation of your organization's general cycle time, while not being impacted by outliers.
Average Calculation:
(Sum of branch times or PR sizes) / (Number of branch times or PR sizes)
75th Percentile Calculation:
(75% are shorter) → 75th Percentile ← (25% are longer)
You can set your LinearB instance to report in either average, median or the 75th percentile in metrics in your account settings. Read more about this feature here: Changing your metrics from average to median or percentile
Where to see your benchmarks
Benchmark indicators are visible on team dashboards as well as in Metrics reports. The main team dashboard will show your overall cycle-time against LinearB's benchmarks. You can see benchmark performance against individual portions of cycle time as well as other metrics
Dashboard View
When enabled a benchmark icon will appear next to the cycle-time metric in a team dashboard.
Metrics Report View
Metrics reports allow you to see your team performance against benchmarks on a metric by metric level. You can even combine multiple teams in a metrics dashboard and see the average performance of the teams against LinearB benchmarks. LinearB benchmarks are available on the following metrics.
- Cycle Time
- Coding Time
- Pickup Time
- Review time
- Deploy Time
- Deploy Frequency
- PR Size
- Rework Rate
Enabling and disabling benchmarks
We understand that benchmarks won't apply or be constructive for all teams. To disable the benchmarks icons for a specific team, go to Team Settings -> General to switch off Engineering Metrics Benchmarks. Make sure to click Save after disabling benchmarks.
