State of DevOps 2025: Review of the DORA Report on AI Assisted Software Development

Key Takeaways

  • AI amplifies your existing engineering culture: accelerating strong, well-structured teams while magnifying dysfunction in struggling ones. Successful adoption depends on robust systems, not just powerful tools.
  • Despite universal dev adoption and clear productivity gains, AI also introduces new fragility and highlights the importance of trust and verification. Teams must balance speed with quality to avoid increased instability.
  • The key to unlocking AI’s benefits lies in applying proven high-performance practices (clear policies, healthy data, and user focus) rather than building a separate AI strategy. Elite organizations will use AI as a catalyst to strengthen culture, processes, and talent development.

For the past year, the technology world has been dominated by a single, seismic question: How will AI reshape software development?

The hype has been deafening, promising a revolution in productivity, creativity, and speed. But for technology leaders on the ground, the reality has been far more complex. The question has evolved from if we should adopt AI to how we can possibly navigate its implementation to realize its staggering potential.

The 2025 DORA Report on the State of AI-assisted Software Development has arrived, and it provides the most definitive, data-backed answer to date. Drawing from nearly 5,000 technology professionals, the report cuts through the noise with a profound and transformative central thesis: AI is not a solution in a box; it's an amplifier.

It is a mirror that reflects the reality of your current engineering culture:

This changes everything. The challenge of successful AI adoption isn't a tools problem — it's a systems problem. This in-depth analysis will break down the report's critical findings, explore the new team archetypes it identifies, and lay out the strategic roadmap for ensuring AI becomes your organization's greatest asset, not its biggest liability.

The state of play: Universal adoption, a "trust paradox," and the fragility of speed

The 2025 report paints a fascinating and complex picture of AI's rapid integration into the daily fabric of software development. Here’s a summary of this complexity:

Pervasive presence

AI is no longer a niche tool for early adopters. A staggering 90% of technology professionals now use AI in their work. It has become a constant companion, with the median user:

The "trust paradox"

Here lies one of the report's most intriguing findings. While over 80% of users report significant productivity gains from AI, a substantial 30% still have little to no trust in the code it generates.

This isn't a sign of failure, but rather one of sophisticated maturity. Developers aren't blindly accepting AI's output. They are treating it as a brilliant but fallible junior partner, applying the same healthy "trust but verify" skepticism they've honed for years with solutions from Stack Overflow or open-source libraries. This nuanced relationship is key to harnessing AI's power safely.

Faster, but more fragile

The 2025 data provides a critical update to last year's findings. AI adoption now clearly and positively correlates with software delivery throughput. Teams are successfully leveraging AI to write and ship code faster. However, this acceleration comes at a cost.

The report also finds that AI adoption continues to correlate with higher instability, leading to more change failures, increased rework, and longer cycle times to resolve issues.

As one analysis aptly puts it, we may be faster, but are we any better? AI is exposing the downstream bottlenecks in testing, code review, and quality assurance that are not equipped to handle this new, accelerated pace.

The AI mirror: Which of the 7 team profiles defines you?

Moving beyond simple performance metrics, the DORA report introduces a groundbreaking diagnostic framework that identifies seven distinct team archetypes. This model provides a holistic, human-centric view of a team's health, performance, and well-being, serving as an "AI Mirror" that reveals your organization's true capabilities.

Understanding your team's profile is the first step toward targeted improvement. Here’s a table of the seven profiles:

Team Profile
% of Industry
Key Characteristics
Foundational Challenges
10%
Stuck in survival mode. Low performance across the board, coupled with high burnout and low trust. Systems are unstable and work is a constant struggle.
The Legacy Bottleneck
11%
Constantly firefighting. Unstable systems and legacy technology create a reactive environment that undermines morale and prevents forward progress.
Constrained by Process
17%
Running on a bureaucratic treadmill. The technology is stable, but restrictive processes, excessive meetings, and red tape kill productivity and lead to high burnout.
High Impact, Low Cadence
7%
The "hero" team. They produce high-quality, impactful work, but their delivery foundation is shaky and unsustainable, often relying on individual heroics rather than solid processes.
Stable and Methodical
15%
The "steady artisans." They prioritize quality and stability above all else, resulting in reliable but slower-paced delivery. They have a strong sense of pride and well-being.
Pragmatic Performers
20%
The reliable workhorses. They consistently deliver with both speed and stability, meeting business goals effectively, but team well-being and trust are only average.
Harmonious High-Achievers
20%
The elite. This group proves that speed, stability, and well-being are not mutually exclusive. They excel across all dimensions, fostering a culture of high trust, performance, and psychological safety.

Crucially, the top two profiles — Pragmatic Performers and Harmonious High-Achievers — represent 40% of the industry. Their success definitively proves that the age-old trade-off between "moving fast" and "not breaking things" is a false dichotomy.

DORA AI Capabilities Model: 7 capabilities to unlock AI's true potential

If AI's value is conditional, how do you create the conditions for it to thrive? The report introduces the DORA AI Capabilities Model, a blueprint of seven practices proven to amplify AI's positive effects and mitigate its risks. The secret is that these aren't exotic, AI-specific tricks. They are the same battle-tested principles of elite DevOps and product management that high-performers have been cultivating for years.

The best strategy to prepare for AI is not to build a separate 'AI strategy' from scratch, but to apply existing high-performance principles to the new context of AI-accelerated development.

  1. Clear and communicated AI stance: Ambiguity creates fear. Leaders must provide psychological safety by establishing a clear, documented policy on the acceptable and encouraged uses of AI tools.
  2. Healthy data ecosystems: AI is only as good as the data it learns from. High-quality, accessible, and unified internal data is the fuel for effective, context-aware AI assistance.
  3. AI-accessible internal data: Don't let your AI tools operate in a vacuum. Connect them securely to your internal code repositories, documentation wikis, and architectural diagrams to give them the context needed to provide relevant and accurate suggestions.
  4. Strong version control practices: The ability to experiment safely is paramount. Disciplined version control, with frequent commits and the ability to easily roll back changes, acts as a crucial safety net, encouraging developers to leverage AI without fear of catastrophic failure.
  5. Working in small batches: This agile principle is more important than ever. Breaking down large, complex problems into small, manageable chunks improves flow, reduces cognitive load, and makes the code review process vastly more effective in an AI-accelerated environment.
  6. User-centric focus: This is the most critical capability of all. Without a relentless focus on delivering value to the end-user, the report warns that AI adoption can have a net-negative impact on team performance. AI can make it easier to build the wrong thing faster than ever before.
  7. Quality internal platforms: To scale the benefits of AI safely, you need "paved roads." A robust internal platform provides the technical guardrails, reusable components, and automated testing that allow development teams to leverage AI's speed without sacrificing stability or quality.

A looming crisis? Defending the talent pipeline

While the report highlights AI's ability to boost developers' sense of pride by automating mundane tasks, it also surfaces a critical threat to the industry's future: the erosion of the traditional apprenticeship model.

Historically, junior engineers learned the craft through the essential, albeit sometimes tedious, tasks delegated to them by senior developers. With AI, a senior developer can now "self-serve," instantly solving a problem they once would have used as a teaching moment for a junior colleague. This removes a vital rung from the learning ladder.

Organizations must address this proactively. Leaders need to design new, intentional training, mentorship, and pairing programs built for an AI-native world to ensure the next generation of engineering talent has a path to mastery.

The final word: Transform your organization, not just your toolchain

The ultimate message of the 2025 DORA report is a profound and urgent call to action. AI does not create elite organizations; it anoints them. It is a powerful, unforgiving mirror that reflects the truth of your existing systems, processes, and culture.

The organizations that win in this new era won't be the ones that simply buy the most AI licenses. They will be the ones that use this technological shift as a catalyst to finally address their foundational challenges — to invest in their platforms, refine their processes, clean up their data, and, most importantly, foster the human-centric culture that enables true excellence. The future isn't about the tool; it's about the team that wields it.

FAQs about DevOps

What is DevOps?
DevOps is a set of practices that combines software development (Dev) and IT operations (Ops) to shorten the development lifecycle and deliver high-quality software continuously.
Why is DevOps important?
DevOps is important because it enables organizations to deliver applications and services at high velocity, improving products faster than organizations using traditional software development and infrastructure management processes.
What are the key benefits of adopting DevOps?
Key benefits of adopting DevOps include faster delivery of features, more stable operating environments, improved communication and collaboration, and more time to innovate.
What challenges do organizations face when implementing DevOps?
Organizations often face challenges such as cultural resistance, lack of skilled personnel, and difficulties integrating new tools and processes when implementing DevOps.
How can organizations measure the success of their DevOps initiatives?
Organizations can measure the success of their DevOps initiatives by tracking metrics such as deployment frequency, lead time for changes, mean time to recovery, and change failure rate.

Related Articles

Security Books & Articles: Must-Read List From InfoSec Experts
Learn
11 Minute Read

Security Books & Articles: Must-Read List From InfoSec Experts

Looking for your next read? Our security experts picked the very best security books, guides & articles. From hobbyists to pros, we’ve got books for you!
Incident Severity Levels 1-5 Explained
Learn
5 Minute Read

Incident Severity Levels 1-5 Explained

Incident severity levels indicate how an incident impacts your customers, so you can prioritize and respond appropriately. Learn how to define and use them.
Cloud Network Monitoring: An Introduction
Learn
4 Minute Read

Cloud Network Monitoring: An Introduction

Network monitoring vs cloud monitoring: do you really need both? Find out why cloud network monitoring is the key to business success in this article.
The Democratization of Data: The Pros & Cons of All That Data
Learn
5 Minute Read

The Democratization of Data: The Pros & Cons of All That Data

Data democratization means that more people have access to data than ever before. Is this good, bad or complicated? Explore the pros and cons of all this data.
Trunk-Based Development vs. GitFlow: Which Source Code Control is Right for You?
Learn
5 Minute Read

Trunk-Based Development vs. GitFlow: Which Source Code Control is Right for You?

Understand trunk-based development and GitFlow, two source code management approaches, so you can decide which is right for your developer environment.
What Is TBD? Trunk-Based Development & Its Role in CI/CD
Learn
5 Minute Read

What Is TBD? Trunk-Based Development & Its Role in CI/CD

Trunk-based development is a popular way to control source code when developing apps. Learn how TBD works, how it supports CI/CD, and when to avoid it.
Status Pages: The Ultimate Guide
Learn
5 Minute Read

Status Pages: The Ultimate Guide

Status pages show real-time status of applications and services. See how these best practices make status pages succeed — and why that’s crucial for business.
When and Why To Adopt Feature Flags
Learn
7 Minute Read

When and Why To Adopt Feature Flags

Learn all about feature flags, a powerful way to fine-tune your control over which features are enabled within a software deployment.
Production Environment Review: The Ultimate Checklist
Learn
4 Minute Read

Production Environment Review: The Ultimate Checklist

Make releases smoother! Check this list for all the areas you want to review in production environments to improve release quality and cadence.