DORA Metrics

Most teams measuring AI coding ROI are looking at the wrong numbers. Developers feel faster, acceptance rates look great, and vendor dashboards show impressive gains — but when you trace those numbers back to shipped features and business outcomes, the story falls apart. The disconnect is real. The METR study found developers felt 24% faster with AI coding tools but were actually 19% slower — and still reported 20% perceived improvement afterward. That gap between perception and reality isn’t just a curiosity; it’s where your ROI evaporates. ...

LinearB’s 2026 Software Engineering Benchmarks Report analyzed 8.1 million pull requests from 4,800+ organizations across 42 countries and found a clear, alarming pattern: agentic AI PRs wait 5.3x longer for review than unassisted human PRs. AI tools generate code faster, but review capacity has not kept pace — creating a bottleneck that erases most of the speed gains. What the LinearB 2026 Benchmarks Actually Measured (8.1M PRs, 4,800 Orgs) The LinearB 2026 Software Engineering Benchmarks Report is one of the largest empirical studies of engineering team performance published this year. It draws on 8.1 million pull requests submitted between January and December 2025 from 4,800 organizations in 42 countries, spanning startups to Fortune 500 enterprises. The report tracks 20 distinct metrics across the entire software delivery lifecycle, and introduces 3 new AI-specific metrics to address the gap left by traditional DORA measurements. These new metrics capture PR Pickup Time by code origin (AI-generated, AI-assisted, or unassisted), code quality scores per PR type, and acceptance rates segmented by generation method. The dataset is large enough to establish statistically significant benchmarks at the 25th, 50th, and 75th percentile tiers, which LinearB labels Developing, Core, and Elite. The 2026 edition is the first to reveal that AI origin of a PR is now the single most predictive variable for PR Pickup Time — more predictive than team size, tech stack, or deployment frequency. ...

AI coding tools ship more code than your review process was ever designed to handle. Faros AI tracked 1,255 engineering teams and found that high AI-adoption teams merged 98% more pull requests — but their PR review times grew 91% longer. More output, yes. But the team is slower, not faster. The 91% Problem: AI Coding Created a New Bottleneck Teams Aren’t Tracking The PR review bottleneck from AI coding tools is one of the most under-tracked drags on engineering velocity in 2026. Teams adopting GitHub Copilot, Claude Code, or Cursor typically measure output — commits, merged PRs, lines shipped — and those numbers look great. What they miss is the queue that forms behind the merge button. According to Faros AI’s analysis of 1,255 engineering teams, high AI-adoption teams are merging 98% more pull requests but experiencing 91% longer PR review times. That means the velocity gain from code generation is being silently absorbed by review lag. Engineering managers celebrating rising commit counts may not realize that their actual deployment frequency and change lead time — the metrics that matter for business outcomes — have flatlined or worsened. The 91% figure is not an outlier. It reflects a structural mismatch: AI tools scale the coding phase while leaving the review phase exactly where it was in 2022. ...

AI developer productivity in 2026 is no longer theoretical — companies like TELUS, Stripe, and Zapier have published hard numbers showing 30–250% productivity improvements, though the data reveals a troubling pattern: individual gains rarely translate to organizational delivery wins without deliberate measurement and workflow redesign. Why Developer Productivity Metrics Are Broken in the AI Era Developer productivity measurement in the AI era is fundamentally broken because the tools that generate value are also the tools that break traditional measurement. DORA metrics — deployment frequency, lead time for changes, change failure rate, time to restore — were designed for human-paced engineering workflows. When Stripe’s autonomous agents merge 1,300 pull requests per week with zero human-written code, deployment frequency spikes without reflecting genuine human productivity. When AI generates 41–46% of all code (GitHub’s 2026 data), lines of code per developer becomes meaningless as a baseline metric. The Harness engineering report found 89% of teams believe their current metrics accurately reflect AI’s impact — yet 94% of those same teams admit key factors like tech debt accumulation, AI validation time, and developer burnout are completely absent from their dashboards. This contradiction is the central measurement crisis in 2026 engineering: orgs feel productive, their tools tell them they’re productive, but the underlying delivery system is flying partially blind. The gap between self-reported and actual gains is real: METR’s survey of 349 technical workers found median self-reported speed increases of 3x, while organizational delivery metrics showed far more modest improvements. Understanding this paradox is the starting point for building measurement that actually works. ...

Faros AI is an engineering intelligence platform that connects GitHub, Jira, and 100+ SDLC tools to give engineering leaders a single, accurate picture of developer productivity and AI coding tool ROI — measured in real financial terms, not vanity metrics. If you’ve deployed GitHub Copilot, Claude Code, or Amazon Q Developer and you’re still answering “so what’s the ROI?” with a shrug, this review is for you. What Is Faros AI? The Engineering Intelligence Platform Explained Faros AI is an engineering analytics platform that unifies data from across the software development lifecycle — version control, issue trackers, CI/CD pipelines, and AI coding assistants — into a single normalized data model. Founded in 2021 and backed by Insight Partners, Faros AI has become the go-to platform for engineering leaders who need to answer board-level questions about AI investment returns. The platform ingests raw telemetry from 100+ integrations and surfaces DORA metrics, sprint health, AI adoption rates, and custom ROI models in a unified dashboard. Unlike simpler DORA tools that track deployment frequency in isolation, Faros correlates AI coding assistant usage patterns with downstream outcomes: does higher Copilot acceptance actually reduce cycle time? Are Claude Code sessions increasing PR volume while also increasing review backlog? In 2026, with 84% of developers actively using AI tools that now generate 41% of all code, that correlation is the question every CTO is asking. Faros AI is purpose-built to answer it at enterprise scale, with a dataset from 22,000 developers across 4,000+ teams to benchmark your results against. ...