Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table
All statistics

Statistics · Published

Agile Adoption Statistics (2026): Adoption, Depth, Outcomes and the AI Shift

Only 13% say Agile is fully embedded across their business, even as 84% use or plan to use AI in delivery.

Compiled by Matt Angerer
25 sources · 9 min read

Agile is now the default delivery model for most software teams, but the public data shows a wide gap between using Agile and running it well. This roundup collects the most-cited figures from 2021 to 2026, with the year and population behind each one. Most current numbers come from Digital.ai's State of Agile series, and older Standish Group and KPMG figures are marked as historical.

Key takeaways

84%

of respondents use or plan to use AI in the development lifecycle (2025)

Source: Digital.ai, October 2025

76%

report rising scrutiny of the business impact and ROI of their Agile work (2025)

Source: Digital.ai, 2025

13%

say Agile is fully embedded across business and technology functions (2025)

Source: Scrum.org commentary on Digital.ai, 2025

39%

of Agile projects were successful in Standish CHAOS data for 2011–2015, versus 11% for Waterfall

Source: Hastie, reproducing Standish Group data, 2015

Adoption: how widely teams use Agile

Adoption numbers swing with the survey wording. Digital.ai's 2021 edition reported that 86% of organizations report agile adoption in software development, based on 1,382 complete responses (historical; figure relayed by TeamRetro). More recent editions ask about the operating model rather than whether a team uses Agile at all. Per Digital.ai's 2025 findings, 74% of organizations now say they use hybrid or homegrown models.

  • In the 18th State of Agile Report, 48% of respondents used hybrid or mixed models and another 26% used a self-developed approach. (Echometer summary)
  • A KPMG study across 17 countries found that 81% of organizations have delivered at least one Agile transformation within the last 3 years. This study is older (the page we reviewed carries no 2026 date), so treat it as historical.
  • In AgileSherpas' 2026 marketing survey, 25% of respondents say they're currently using Agile marketing, and another 25% are past users. The survey ran from December 2025 through February 2026 and is vendor-run.
  • Plaky's summary of the 17th edition reports that almost 70% of organizations report these departments adopting Agile for IT and software delivery (historical, 2023 edition).

Depth: Agile embedded or bolted on?

Adoption is broad but shallow. The 2025 report found that most organizations have not reached a deep, enterprise-wide practice. Business leaders are the weakest link: only 15% of business leaders participate meaningfully in Agile practices, and leadership alignment is now one of the top blockers to success.

13%
15%

Source: Scrum.org commentary on Digital.ai 18th State of Agile Report, 2025

  • Only 13% of respondents in a KPMG survey said top management fully supports their agile transformation. The year is not stated in the summary we reviewed (Parabol, citing KPMG).
  • Parabol's summary of the same KPMG work adds that 38% of respondents in a KPMG survey stated that their agile transformation has no support from top management.
  • In an earlier KPMG survey, culture and performance management was consistently the challenge felt most strongly by respondents, regardless of how long they had been transforming or their maturity. (KPMG Belgium, 2021)
  • Digital.ai's 2025 data shows 33% say agile is treated as a delivery function rather than a strategic lever.
  • 26% of Agile leaders influence product or portfolio planning decisions. (Peak Digital summary, 2025)

Frameworks: scaling, hybrid and the SAFe question

SAFe is the most visible scaling framework, but its share has moved around. Digital.ai's 2025 edition says SAFe usage has rebounded to 44% (down from 53% at its peak but up from last year's low of 26%). The same edition notes adoption of Scrum@Scale, LeSS, and Nexus declined. The chart below combines the 2025 figures with a Scrum@Scale figure from a secondary summary.

SAFe, peak (year not stated in source)53%
SAFe, prior-year low26%
SAFe, 202544%
Scrum@Scale and Scrum of Scrums, 202523%

Source: Scrum.org on Digital.ai, 2025; Scrum@Scale figure via Breeze, 2026

  • An academic survey of software practitioners found that SAFe is the most widely adopted framework among our respondents. The paper's respondents numbered n=100, 49%, who had adopted SAFe as their primary framework (ACM, 2021).
  • Scaled Agile's own vendor survey reports that 83% of respondents said their organization are adapting SAFe (2025 State of SAFe, vendor data, not independent).

Value and ROI pressure

Funding is still moving, but leaders want proof. Digital.ai's 2025 report says 76% of organizations report increased scrutiny on the business impact and ROI of their Agile practices. The same report says nearly one-third (29%) are now accountable for tying Agile work to business outcomes, while more than one-quarter (26%) are doing less coaching or framework evangelism.

  • 52% can't measure business outcomes effectively, and 53% struggle to prioritize work because their insights are unreliable (Digital.ai 2025, as summarized by Rebel Scrum).
  • Within the same report, 55% say they have end-to-end SDLC visibility, while 65% say their toolchain is well aligned.
  • Plaky attributes to the 18th report that 41% of organizations increased their investment in Agile in the last 1–2 years. We could not confirm that figure in the Digital.ai PDF, so treat it as secondary.
  • In AgileSherpas' marketing survey, 87% of Agile marketers say Agile improved their productivity.

Project outcomes: what the Standish CHAOS data shows

The Standish Group's CHAOS research is the most cited source on Agile versus Waterfall outcomes, but its full reports are paywalled and the numbers are often republished in different forms. The 2015 cut that a 2021 academic paper reproduced covers outcomes of more than 10,000 projects between 2011 and 2015.

Successful, all sizes: Agile39%
Successful, all sizes: Waterfall11%
Successful, large projects: Agile18%
Successful, large projects: Waterfall3%

Source: Hastie, reproducing Standish Group CHAOS 2011–2015 data, 2015

Failed, all sizes: Agile9%
Failed, all sizes: Waterfall29%
Failed, large projects: Agile23%
Failed, large projects: Waterfall42%

Source: Hastie, reproducing Standish Group CHAOS 2011–2015 data, 2015

  • The Standish 2015 report itself found that projects using agile have almost four times the success rate of waterfall projects, and waterfall projects have three times the failure rate.
  • Secondary reporting of the 2020 edition says software projects using Agile methods are three times more likely to succeed than those using the Waterfall method. We could not open the 2020 report itself.
  • Across all project types, in 2015, 29% of projects were successful and 19% failed. By 2020, the success rate had increased slightly to 31%, while the failure rate remained at 19% (arXiv review citing CHAOS).
  • For large initiatives, one Latvian IT case study cites Standish-based data that large and very large projects with teams of more than 30 people and project duration of more than 1 year produce on average only 4% success. This is a secondary citation, and it applies to all methods, not Agile alone.

Source: 1994 figure via ResearchGate paper on CHAOS figures; 2015 and 2020 via arXiv review of CHAOS data, 2023

Testing and quality signals

Quality is where the Agile story gets uncomfortable. Digital.ai's 2025 edition reports that 63% report declining software quality, and teams say they're delivering slower, even with better reporting. That result sits next to a shift in pressure: quality and security integration another 69% of organizations report it as a factor shaping their work.

  • 60% use agile assessments or health checks run by internal teams or external partners (Digital.ai 2025, via TeamRetro).
  • In KPMG's older transformation data, 56% of organizations undergoing agile transformations believe their architecture and tooling do not support continuous delivery. Parabol relays this figure without a year.

People, roles and skills

  • Digital.ai's 2025 respondents describe roles bifurcating: some moved toward business accountability, others toward less coaching.
  • 23% of agile practitioners have picked up AI stewardship as a new responsibility (Digital.ai 2025, via TeamRetro).
  • In KPMG's undated survey, only 17% of survey respondents agreed that their performance management systems support agile ambitions.

AI in agile delivery

AI is the dominant theme of the 2025 State of Agile report. 84% are using or planning to use AI in the development lifecycle, and 1 in 4 already have agentic AI pilots doing actual decision-making. Adoption rose quickly: 84% AI adoption rate among Agile practitioners in 2025, up from 68% the year before. Governance has not kept pace. 49% have governance guardrails in place for AI use inside Agile delivery. Digital.ai's own summary reads: "AI without strong data governance creates acceleration without alignment."

84%
49%
18%

Source: Digital.ai, 2025; 49% via Peak Digital summary, 2025; 18% via TeamRetro summary, 2025

Marketing teams show the same split. In AgileSherpas' 2026 survey, Agile marketers are three times more likely than non-Agile marketers to have AI fully integrated into their marketing processes: 39% versus 13%.

AI fully integrated: Agile marketers39%
AI fully integrated: non-Agile marketers13%

Source: AgileSherpas, 2026 State of Agile Marketing (430 marketers, Dec 2025–Feb 2026)

Where the numbers disagree

  • Adoption rate. TeamRetro relays 86% (Digital.ai, 2021). Staragile reports around 94-95% of organizations report using Agile practices to some extent, and elsewhere on the same page around 97% of organizations report using Agile development methods to some extent. These answer a looser question than "fully embedded," and we could not trace the 94–97% figures to a primary report.
  • Sample size. Digital.ai's respondent base has shrunk sharply. One analysis reports this year's (2025) survey had 349 respondents. Last year (17th report from 2024) had 788 people. The year before that had 3,220. Year-over-year changes in the report are less stable than the headlines suggest.
  • Standish success rates. The 2015 cut (39% Agile success) differs from a secondary summary covering 2013–2020 that gives Agile projects, on average, a 42% success rate, while Waterfall projects lag significantly behind at 13%. Researchers have also argued that Standish's successful and challenged project results are indeed meaningless for benchmarking.
  • Stress outcomes. AgileSherpas gives two different figures for stress: 77% communicated lower stress levels in one place and 66% of Agile marketers reported lower stress levels in another.

What this means for your sign-off

  • Confirm the operating model before you confirm the test plan. Most organizations run hybrid or homegrown models, so a sprint-based test plan may not match the release train your SAP program uses. Map sign-off gates to the SAP Activate phases your team actually follows; see SAP Activate and the RISE with SAP methodology.
  • Get a named business owner for exit criteria. With only 15% of business leaders meaningfully involved in Agile practice, test exit criteria are at risk of being set by the testing team alone. Put business owners on the hook for signing defect thresholds and process coverage. The SAP Testing Center of Excellence playbook covers how to structure that ownership.
  • Measure outcomes, not just throughput. When 76% of organizations face ROI scrutiny and 52% cannot measure business outcomes well, velocity and story-point reports will not survive a sign-off review. Tie regression coverage to business processes and to defect escape rates.
  • Set AI guardrails before AI touches test artifacts. With 84% using or planning AI and 49% having guardrails, the gap is the risk. Use an acceptable-use policy and a review log for AI-generated tests; the template library includes both. For broader context on AI in SAP delivery, see SAP AI for practitioners.
  • Automate in a deliberate order. Frequent releases make regression the bottleneck. Start with the stable, high-volume business processes; the S/4HANA regression automation guide sets out that order.
  • Treat published figures as context, not targets. The Standish and KPMG numbers are dated, partly secondary, and sometimes inconsistent. Cite them with year and population, or leave them out of a steering-committee deck.

Frequently asked questions

What share of organizations use Agile?

It depends on the question. Digital.ai's 2025 report says 74% of organizations now say they use hybrid or homegrown models, while its 2021 edition reported 86% of organizations report agile adoption in software development. The 2021 figure is historical.

Do Agile projects succeed more often than Waterfall projects?

The Standish 2015 data, as reproduced in a 2015 paper, shows Agile 39% successful, 52% challenged, 9% failed; waterfall 11% successful, 60% challenged, 29% failed. A secondary summary of the 2020 edition reports a threefold success advantage, but the original is paywalled and the figures conflict across sources.

How many business leaders are involved in Agile?

According to Digital.ai's 2025 report, only 15% of business leaders participate meaningfully in Agile practices.

How common is AI in Agile delivery?

In Digital.ai's 2025 report, 84% are using or planning to use AI in the development lifecycle, but 49% have governance guardrails in place for AI use inside Agile delivery.

Is SAFe the most common scaling framework?

It is the most cited. Digital.ai's 2025 edition put SAFe usage at 44%, down from a peak of 53%. An academic survey of 100 practitioners in 2021 found SAFe was the most widely adopted framework among its respondents, though that sample is small.

Are there SAP-specific Agile adoption statistics?

We did not find a published SAP-specific agile adoption survey in this review. The figures above are cross-industry, and the closest proxies are the operating-model and governance numbers from Digital.ai's 2025 report.

Sources

  1. The 18th State of Agile Report (PDF), Digital.ai, 2025
  2. Digital.ai 18th State of Agile Report press release, Digital.ai via Business Wire, October 2025
  3. 18th State of Agile Report commentary, Scrum.org, 2025
  4. State of Agile 2025: 84% Use AI, 49% Have Governance, Peak Digital, 2025
  5. 18th State of Agile Report (2025): 10 Key Insights, Pawel Rola, 2025
  6. 18th State of Agile Report commentary, Rebel Scrum, 2025
  7. 178 Agile, Scrum & Retrospective Statistics (2026), TeamRetro, 2026
  8. Scrum Statistics 2026, Echometer, 2026
  9. Agile and Scrum statistics you need to know (2026), Breeze, 2026
  10. Agile Statistics: Verified Data on Adoption & Success Rates, Plaky, 2026
  11. Project Success in Agile Development Projects, arXiv, 2017 (reproduces Standish CHAOS 2011–2015 data)
  12. CHAOS Report 2015, Standish Group, 2015
  13. Project Management, INFORMS, 2024 (secondary summary of the 2020 CHAOS report)
  14. Simulating the Software Development Lifecycle: The Waterfall Model, arXiv, 2023
  15. The rise and fall of the Chaos report figures, ResearchGate, historical paper
  16. Agile vs. Waterfall: Comparing Success Rates in Project Management, Agile Genesis, secondary summary of CHAOS 2020
  17. Project Managers Fail to Help Software Projects (Standish Group Chaos 2020), Medium, secondary summary
  18. Application of LEAN Principles to Improve Business Processes, arXiv, 2020
  19. 300+ Agile and Scrum Statistics for 2026, Parabol, 2026 (secondary summary of KPMG data)
  20. Agile transformation: the common challenges, misconceptions and drivers, KPMG, 2021
  21. Agile working is becoming a strategic transformation priority, Consultancy.eu, reporting on a KPMG study (undated, historical)
  22. Why Do Organizations Adopt Agile Scaling Frameworks? A Survey of Practitioners, ACM, 2021
  23. SAFe 101: A Beginner's Guide to the Scaled Agile Framework, Medium, 2026 (cites Scaled Agile vendor survey)
  24. 2026 State of Agile Marketing Report, AgileSherpas, 2026
  25. State of Agile 2026: Insights, Trends, and Key Findings, StarAgile, 2026 (secondary; used for conflicting adoption figures)

Last updated: November 10, 2026. Statistics are refreshed as new research is published.

More statistics

How this page is made: statistics are gathered from published research with AI-assisted search, every figure is linked to its source, and the page is refreshed as new data is published. Found an error? Tell us.