The sixth annual State of DevOps Report — covering responses from over 27,000 technology professionals — reinforced and expanded on what the industry already suspected: the gap between high-performing and low-performing IT organizations is not narrowing. If anything, it is growing in the areas that matter most. Below are five of the most actionable takeaways from the 2017 data.
1. Automation Remains the Single Biggest Differentiator
Automation has always been a cornerstone of DevOps practice, but the 2017 report reinforced its status as a key differentiator between high and low performing organizations. High performers automate significantly more of their software delivery pipeline — configuration management, testing, deployments, and change approvals — than their lower-performing counterparts who still rely heavily on manual processes.
The report highlights two primary outcomes of widespread automation:
- Accelerated feedback loops — Faster, automated testing and integration cycles surface defects earlier, improving both product quality and release cadence.
- More engineering time for valuable work — When teams stop manually provisioning servers or shepherding change-approval tickets, they redirect that energy toward product development.
There is a third, often overlooked, benefit worth calling out explicitly: automation is auditing. Automated pipelines are inherently consistent, repeatable, and loggable. Every build, test cycle, deployment, and release generates structured logs automatically. Over time, this log trail becomes your audit record, your security event log, and your compliance evidence — produced as a natural by-product of doing the work, not as a separate overhead task.
2. Connect Your Automation Dots — End to End
Many enterprises have already made progress on automation, but typically in isolated pockets: one team automates deployments, another automates testing, a third automates infrastructure provisioning. These silos of automation deliver local value but limit organisation-wide benefit.
The 2017 report underscores the importance of moving from disconnected automation islands to an integrated, end-to-end delivery pipeline. Connecting your toolchain — from development and testing through operations, security, and business metrics — is how DevOps scales beyond individual teams.
This does not mean forcing every team onto a single tool. Teams can and should retain the freedom to choose the best tool for their specific job. What matters is the ability to orchestrate and integrate those tools so they feed into a shared pipeline. That shared pipeline provides visibility, governance, and traceability across the entire value stream — something no collection of isolated tools can achieve on its own.
3. Are You Just Releasing Bad Code Faster?
One of the most striking findings in the 2017 report is the diverging performance profile between high and low performers when it comes to throughput versus stability.
The headline numbers for high performers are significant:
- 46× more frequent deployments than low performers
- 440× faster lead time from commit to deploy (roughly one hour versus one week to one month)
- 96× faster mean time to recovery (MTTR) from downtime
- 5× lower change failure rate
What is particularly telling is how the gap has shifted since 2016. Low performers did improve their deployment frequency — moving from roughly once per month to once every six months in 2016, up to once per week to once per month in 2017. That is genuine progress on throughput. However, the stability gap simultaneously widened. In 2016, high performers recovered from outages 24× faster than low performers. By 2017, that gap had grown to 96×. The change failure rate gap also grew, from 3× to 5×.
The pattern is clear: low performers invested in shipping faster but did not invest proportionally in testing, quality gates, and reliability practices. The result is faster delivery of lower-quality software. Speed without quality is not a DevOps win. Shifting testing, monitoring, and security checks left — earlier in the pipeline — is essential to ensure that deploying more frequently also means deploying more reliably.
4. De-coupling Is the Architecture Strategy That Enables Continuous Delivery
The 2017 data confirms that Continuous Delivery (CD) significantly reduces deployment pain and correlates strongly with higher IT performance. More importantly, the report identifies the architectural preconditions that make CD possible at scale.
The strongest predictors of Continuous Delivery success are:
- Lean, autonomous, empowered teams that can make decisions without extensive cross-team coordination
- Loosely coupled services that can be developed, tested, and deployed independently of one another
This applies both at the organisational level (team topology) and the technical level (system architecture). When services and teams are tightly coupled, every change requires synchronisation across multiple groups, creating bottlenecks that undermine deployment frequency and increase risk.
Many enterprises are actively decomposing monolithic applications into microservices or service-oriented architectures, adopting containers, and restructuring teams to match. However, these are not overnight transformations. Most large organisations operate in a hybrid state simultaneously — supporting legacy monoliths alongside modern microservices, virtual machines alongside containers, traditional release processes alongside CD pipelines. The practical challenge is ensuring your tooling and platform strategy can accommodate this hybrid reality rather than forcing a premature or disruptive all-or-nothing migration.
5. Transformational Leadership Has a Measurable Impact on DevOps Performance
DevOps transformations succeed or fail based in large part on the quality of leadership supporting them. The 2017 report draws on the Rafferty and Griffin Transformational Leadership model to define five leadership characteristics that correlate most strongly with high IT performance:
- Vision — A clear, credible picture of where the organisation is heading
- Inspirational communication — Motivating teams through consistent, compelling messaging
- Intellectual stimulation — Encouraging curiosity, experimentation, and learning
- Supportive leadership — Removing blockers and advocating for team needs
- Personal recognition — Acknowledging individual and team contributions meaningfully
The report finds that high, medium, and low performing organisations show statistically significant differences across these five dimensions. In other words, leadership quality is not just a cultural nicety — it is a measurable variable in IT performance outcomes.
For practitioners, this data provides two concrete actions:
- Assess your leadership against these five dimensions to identify specific gaps that may be limiting your DevOps progress.
- Invest intentionally in leadership development — coaching, mentoring, and organisational design choices — focused on these demonstrable, measurable characteristics rather than on abstract culture statements.
The Overarching Message
The 2017 State of DevOps Report is consistent with prior years in confirming that high performers do not achieve their results by accident. They automate broadly and deliberately, connect their toolchains into coherent pipelines, invest equally in stability and throughput, architect for independence, and cultivate leadership that actively enables their teams. Low performers who focus exclusively on shipping faster — without building quality, reliability, and architectural flexibility into their foundation — are not closing the gap. They are widening it.
Original analysis sourced from news.sys-con.com commentary on the 2017 Puppet / DORA State of DevOps Report.