Research Digest · October 2026

Accelerating Software Delivery with AI

By Mladen Malkovich, Partnered Solutions LLC · Published October 2026 · Last reviewed October 2026 · Next review January 2027

What independent evidence says about where acceleration comes from, why most organizations don't manage to accelerate, and the five things top teams do to accelerate.

Download the PDFRead it online

No formFree to share in full124 sources · 53 organizations · 7 pages

Seven pages of summarized evidence for executives, board members, investors, and the advisors who brief them, with a complete list of 124 sources from 53 organizations in the appendix. Evidence window 2022 – September 2026, weighted toward controlled trials and large-scale telemetry.

Executive summary

Page one of the report

The tools are necessary, but the return comes from people and process. Key findings are synthesized into one actionable sentence:

To accelerate delivery, invest in your people's AI skills and enable them to reimagine your processes with AI.

Four findings carry that argument, and each has a section behind it.

1
The fact

Only one team in twenty gets to 2x acceleration with AI.

  • Across 22,000 organizations, the median team's delivery throughput rose 4% with AI; the top 5% of teams roughly doubled (CircleCI).
  • Individual engineers using AI in their own way are 10–25% faster on real work, but the organization typically gets 0–10%: coding is only 25–35% of idea-to-launch, and the gains that do appear are absorbed downstream by review queues, larger changes, rework, and incidents.
  • Engineers also overestimate their own gain — self-assessed productivity correlates with measured output at just 0.17 (Stanford).
→ Sections 1 and 2
2
The cause

People and process impact the result two to four times more than technology.

  • Four independent studies agree: a clear AI strategy lifts measurable impact by about 25 points against about 5 for better tools (BCG); organizational factors explain 67% of AI impact against 32% for individual factors (Microsoft); 73% of AI high performers redesigned workflows against 25% of others (McKinsey); technology is about 20% of an initiative's value (PwC).
  • And it does not fix itself: 81% of organizations provide AI tools, 46% provide training; 84% of developers use AI, 29% trust its output; every tool generation makes unmanaged use faster and messier — bugs per developer +9% → +54%, median review time +91% → +441% (Faros).
→ Section 3
3
The moves

The teams that accelerate do five things, and none of them is buying another tool.

Leadership
Leadership decides at the top — strategy, investment, a named initiative, a baseline and target, and where saved time goes.
People
People are coached hands-on, on real work: competence to direct AI, confidence to use it, and the ability to explain and vouch for the result.
Practice
Intent is made explicit — context, specs, standards and rules files become the new control surface, written down so the practice lives across the team, not in two people.
Quality
Review and verification are re-engineered for AI volume — risk-tiered review, tests with every change, a human in control.
Workflows
Workflows are redesigned before the tools scale — the whole lifecycle, with product management and QA inside it.
→ Section 4
4
The payoff

With those five in place, the same teams deliver 2x+.

  • Organizations that redesign how work flows reach +25% to +30% productivity and faster time-to-market (Bain, McKinsey).
  • The top 5% of teams roughly double (CircleCI).
  • An enterprise mandate paired with standardized tooling and re-engineered review reached 2.09x throughput with merge and revert rates stable (Stanford/CMU, 802 developers).
→ Section 5

How to read the report. Section 1 gives the ranges and the confidence behind them; Section 5 puts the payoff in one table (Table 3). Section 2 explains why individual gains do not reach the organization. Section 3 gives the cause and the five barriers, one number each. Section 4 outlines the five things the teams that accelerate do, with evidence for each. Section 5 is the five questions and the payoff. The appendix lists all 124 sources with links.

Download the PDFRead it online
What's inside

Seven pages, five sections

  • Section 1 — The fact: only 1 out of 20 teams gets to 2x, with the confidence behind each range and the trend in numbers.
  • Section 2 — why individual gains do not reach the organization.
  • Section 3 — The cause: people and process, and the five barriers that hold most organizations back.
  • Section 4 — The moves: the five things, what each means in practice, and the evidence for each.
  • Section 5 — The payoff, and five questions to ask your technology leaders and teams.
  • Evidence and how to read it · Appendix: all 124 sources with links.
The sources

124 sources, 53 organizations, 9 kinds of evidence

Analyst firms (Forrester, Gartner, HFS Research, Info-Tech); consultancies (Bain, BCG, Capgemini, Deloitte, EY, KPMG, McKinsey, Prosci, PwC, Thoughtworks); universities and labs (Carnegie Mellon, Chalmers, METR, Northeastern, Stanford, UC Berkeley, Victoria; 20+ peer-reviewed studies); technology and AI companies (AWS, Anthropic, Atlassian, GitHub, GitLab, Google/DORA, JetBrains, Microsoft, Stack Overflow); engineering-intelligence platforms (CircleCI, DX, Faros AI, GitClear, Harness, Jellyfish, LinearB, Sonar, Uplevel, Veracode); testing and quality platforms; professional bodies; product and practitioner sources.

Every source had a stated method, a stated sample and a quantified result; controlled trials and large-scale telemetry are weighted first, vendor self-reports last.

Prepared by Mladen Malkovich · Partnered Solutions LLC. Independent evidence and AI Sprints program measurements are kept separate throughout; the report carries no program figures. Last reviewed October 2026 · next review January 2027.

Find out where your teams sit against the 2x benchmark.

A 45-minute benchmarking and planning call. You leave with a baseline we can measure against, an ROI target set before any spend, and the shape of a first cohort — roles, format, dates. No preparation needed beyond deciding who should be in the room.

Schedule a callRead the report