State of DevOps 2024: Key Findings from Google’s DORA Accelerate Report

Software Delivery Performance: The Four Key DORA Metrics in 2024

At the core of every state of devops 2024 analysis are DORA’s four key metrics, which have been validated repeatedly as the most effective measures of software delivery performance. These metrics capture both the throughput and stability of the software delivery process:

• Change Lead Time: The time it takes for a code commit or change to be successfully deployed to production
• Deployment Frequency: How often application changes are deployed to production
• Change Failure Rate: The percentage of deployments that cause failures in production, requiring hotfixes or rollbacks
• Failed Deployment Recovery Time: The time it takes to recover from a failed deployment

A significant evolution in the 2024 report is the introduction of a fifth metric: rework rate, which measures unplanned deployments performed to address user-facing bugs. DORA’s analysis confirmed that rework rate and change failure rate are related, and together they create a reliable factor of software delivery stability. This distinction separates software delivery into two complementary factors: throughput (change lead time, deployment frequency, failed deployment recovery time) and stability (change failure rate, rework rate).

This refined framework provides a more nuanced understanding of team performance. More than half of the teams studied show differences between their throughput and stability scores, suggesting that optimizing for speed alone — without attention to stability — yields incomplete results. The most effective teams achieve excellence in both dimensions, aligning with DORA’s full capabilities framework.

Elite vs. Low Performers: The State of DevOps 2024 Performance Gap

The 2024 report identifies four distinct performance clusters through statistical cluster analysis, and the gap between the best and worst performers is staggering. When compared to low performers, elite performers achieve:

• 127x faster change lead time
• 182x more deployments per year
• 8x lower change failure rate
• 2,293x faster failed deployment recovery times

A critical insight from the state of devops 2024 data is that industry does not meaningfully affect performance levels. DORA’s research rarely finds that industry is a predictor of software delivery performance — high-performing teams exist in every industry vertical. This means that no organization can legitimately attribute poor performance to industry-specific constraints. The path to elite performance is available to every team willing to invest in continuous improvement.

The report emphasizes that improvement matters more than reaching a specific performance level. The best teams are those that achieve “elite improvement” through iterative, incremental practices rather than simply chasing metrics. This philosophy aligns with the broader DevOps best practices that prioritize continuous learning over static benchmarks.

AI Adoption in Software Development: The 2024 Inflection Point

The most significant theme in the state of devops 2024 report is the rapid, industry-wide adoption of artificial intelligence in software development. The data tells a compelling story of transformation at both organizational and individual levels:

Organizational adoption: 81% of respondents reported that their organizations have shifted priorities to increase AI incorporation into their applications and services. 49.2% described this shift as “moderate” or “significant.” Only 3% reported a decrease in AI focus — within the margin of error. Notably, 78% of respondents trust their organizations to be transparent about how they plan to use AI.

Individual adoption: 75.9% of development professionals rely on AI in one or more daily professional responsibilities. Adoption is remarkably uniform across all industry sectors, although respondents in larger organizations report slightly less AI reliance than those in smaller firms — consistent with research showing larger organizations adapt more slowly to technological change due to higher coordination costs.

The most common AI use cases in development work include writing code (74.9%), summarizing information (71.2%), explaining unfamiliar code (62.2%), optimizing code (61.3%), documenting code (60.8%), writing tests (59.6%), debugging code (56.1%), and data analysis (54.6%). Chatbots are the most common AI interface (78.2%), followed by external web interfaces (73.9%) and IDE-embedded AI tools (72.9%).

AI’s Impact on Developer Productivity and Performance

The productivity benefits of AI adoption are substantial but nuanced. 75% of respondents reported positive productivity gains from AI, with more than one-third describing these gains as “moderate” (25%) or “extreme” (10%). Fewer than 10% reported any negative productivity impact. Security professionals, system administrators, and full-stack developers reported the largest productivity improvements.

However, the state of devops 2024 findings include important cautionary signals. While AI boosts perceived productivity, flow, job satisfaction, code quality, documentation, review processes, team performance, and organizational performance, it also produces some detrimental effects:

• Reductions in software delivery performance metrics — suggesting that AI-assisted work may introduce hidden complexity or quality issues
• Uncertain impact on product performance — the net effect on end-user experience is not yet clear
• Decreased time spent on valuable work — a paradoxical finding where individuals report spending less time on high-value tasks despite AI adoption, possibly because AI-generated output requires additional review and refinement cycles

The competitive pressure driving adoption is intense. Interview participants frequently linked AI adoption to competitive necessity, with developers describing AI proficiency as “the new bar for entry as an engineer.” Organizations are forgoing normal procurement bureaucracy because they fear competitors will gain advantage first. This pressure creates risk: adoption driven by fear rather than measured assessment of value may lead to suboptimal implementations. Understanding how to manage technology transitions effectively is essential in this environment.

Platform Engineering and Its Impact on State of DevOps 2024 Outcomes

Platform engineering has emerged as a significant lever for improving developer productivity and organizational performance in the state of devops 2024 landscape. Well-designed internal developer platforms reduce cognitive load, streamline workflows, and create standardized paths to production that enable teams to focus on delivering value rather than managing infrastructure complexity.

The DORA report finds that platform engineering has a measurably positive impact on both productivity and organizational performance. Teams that leverage well-architected internal platforms report improved efficiency, faster onboarding for new team members, and more consistent deployment practices. Platform engineering also helps enforce security, compliance, and governance standards without creating friction in the developer workflow.

However, the report includes cautionary signals about platform engineering’s impact on software delivery performance metrics. This suggests that the benefits of platforms may come at the cost of additional abstraction layers that can slow certain delivery metrics, particularly for teams that were already highly optimized. The key insight is that platform engineering must be approached as an enabler — not a mandate — and should be continually refined based on developer feedback and usage patterns.

Organizations investing in platform engineering should focus on self-service capabilities, clear documentation, and iterative improvement based on real developer needs. The Platform Engineering community provides frameworks for getting started, while DORA’s own Quick Check tool helps teams assess their baseline before making infrastructure investments.

Transformational Leadership and Organizational Stability

One of the most actionable findings in the state of devops 2024 report is the profound impact of transformational leadership and organizational stability on every outcome measured. Transformational leaders — those who inspire, challenge, and develop their teams — drive improvements across every metric: employee productivity, job satisfaction, team performance, product performance, and organizational performance, while simultaneously decreasing employee burnout.

The data on organizational stability is equally striking. Unstable organizational priorities lead to meaningful decreases in productivity and substantial increases in burnout, even when organizations have strong leaders, good documentation, and a user-centric approach to software development. This finding is critical: no amount of technical excellence can compensate for constantly shifting priorities.

For engineering leaders, the implication is clear. Protecting team focus by providing stable priorities, clear strategic direction, and shielding from organizational churn is not a luxury — it is a prerequisite for high performance. Teams that are constantly pivoting cannot build the deep expertise, automated pipelines, and feedback loops that characterize elite DevOps organizations.

The report also highlights user-centricity as a key driver of performance. Organizations that prioritize the end-user experience produce higher quality products, with developers who are more productive, satisfied, and less likely to experience burnout. This reinforces the principle that technical teams should be organized around user outcomes, not internal organizational boundaries.

Developer Experience: The State of DevOps 2024 Focus on People

The 2024 DORA report dedicates significant attention to developer experience — the overall satisfaction, productivity, and well-being of the people building software. This reflects DORA’s decade-long evolution from purely technical metrics to a holistic understanding of what drives software delivery excellence.

The key outcomes measured include burnout (emotional, physical, and mental exhaustion), flow (the amount of focus achieved during development tasks), job satisfaction, and individual productivity (the extent to which someone feels effective and efficient). These human outcomes are not soft metrics — they directly predict team performance, product quality, and organizational success.

The state of devops 2024 data shows that these outcomes are interconnected and mutually reinforcing. Teams with high flow states produce better software, experience less burnout, and report higher job satisfaction. Conversely, burnout erodes every aspect of performance and is strongly linked to unstable priorities and poor leadership. Organizations that invest in developer experience create virtuous cycles that compound over time, while those that neglect it face degenerating spirals of attrition, quality problems, and missed deadlines.

Practical strategies for improving developer experience include reducing toil and manual processes, investing in toolchain quality and developer platforms, providing learning and growth opportunities, ensuring stable team structures and priorities, and creating psychological safety for experimentation and failure. These investments yield returns far beyond individual productivity — they drive the organizational capabilities that separate elite performers from the rest.

Cloud Adoption and Infrastructure Flexibility in 2024

The state of devops 2024 report reinforces a nuanced finding about cloud adoption: flexible infrastructure can increase organizational performance, but simply migrating to the cloud without adopting the flexibility that cloud offers may be more harmful than remaining in the data center. Successful cloud adoption requires transforming approaches, processes, and technologies simultaneously.

This finding challenges the common assumption that cloud migration is inherently beneficial. Organizations that lift-and-shift workloads without rethinking their deployment practices, infrastructure management, and team structures often inherit the worst of both worlds — the cost and complexity of cloud without the agility benefits. The key is adopting cloud-native practices including Infrastructure-as-Code, automated scaling, container orchestration, and on-demand environments.

For organizations evaluating their technology infrastructure strategy, the DORA data provides a clear message: the technology platform matters less than how effectively your teams leverage its capabilities. A well-optimized on-premises environment with strong automation can outperform a poorly configured cloud deployment. The goal should be infrastructure flexibility that enables fast feedback loops, rapid experimentation, and reliable deployments — regardless of where workloads physically run.

A Decade of DORA: Lessons from 10 Years of DevOps Research

As the tenth annual report, the state of devops 2024 edition carries special significance. Over a decade, DORA has surveyed more than 39,000 professionals across organizations of every size and industry globally, building the most comprehensive longitudinal dataset on software delivery performance in existence.

The enduring lessons from this decade of research include several principles that have been consistently validated. First, capabilities — not tools — predict performance. DORA has repeatedly shown that adopting specific practices and building organizational capabilities drives outcomes, while merely purchasing tools does not. Second, culture matters as much as technology. Organizational culture, leadership quality, and team dynamics are as strong predictors of delivery performance as any technical practice.

Third, continuous improvement outperforms big-bang transformations. The teams that achieve the greatest sustained improvements are those that adopt an iterative approach: measure the baseline, hypothesize an improvement, implement it, measure the result, and repeat. Fourth, the metrics work across contexts. Despite variations in technology stacks, industries, regulatory environments, and team sizes, the four key metrics consistently provide actionable insight into software delivery health.

DORA recommends an experimental approach: identify an area you want to improve, measure your current state using the DORA Quick Check, develop hypotheses, commit to a plan, execute, and re-measure. Teams that build this practice of continuous improvement see compounding benefits over time. The DORA Community at dora.community provides forums for sharing experiences and learning from others’ improvement journeys.

Practical Recommendations for Engineering Leaders

Based on the state of devops 2024 findings, here are the highest-impact actions engineering leaders should prioritize:

Measure and Benchmark Software Delivery Performance

Establish baseline measurements using DORA’s four key metrics plus rework rate. Track both throughput and stability as separate factors. Use the performance clusters for benchmarking but focus on improvement rate rather than absolute level. Conduct value stream mapping exercises to identify bottlenecks.

Adopt AI Strategically, Not Reactively

Encourage AI adoption for high-value use cases like code writing, summarization, and debugging, but implement robust quality assurance processes for AI-generated output. Build organizational awareness of AI’s limitations — particularly the trust gap and potential negative impacts on software delivery metrics. Invest in upskilling developers to effectively evaluate and refine AI output rather than blindly accepting it.

Invest in Platform Engineering and Developer Experience

Build internal developer platforms that reduce cognitive load and create standardized paths to production. Prioritize self-service capabilities and iterate based on developer feedback. Measure developer experience outcomes including flow, satisfaction, and burnout alongside technical metrics. Recognize that developer experience improvements drive all other performance outcomes.

Stabilize Priorities and Practice Transformational Leadership

Protect teams from organizational churn by providing stable priorities and clear strategic direction. Invest in leadership development that emphasizes inspiration, challenge, and growth. Create a culture of user-centricity that connects engineering work to user outcomes. Build psychological safety that enables experimentation, learning from failure, and continuous improvement.