This article is an independent summary of the themes discussed at the 2016 DevOps Enterprise Summit (DOES16) in San Francisco, based on the teaser published by Electric Cloud in November 2016. The original full post appeared on the Electric Cloud blog.
From Grassroots Movement to Enterprise Priority
For much of its early history, DevOps was associated with high-growth technology startups — the so-called “unicorns” — that had the freedom to build culture and tooling from scratch. Traditional enterprises, burdened with legacy systems, regulatory requirements, and large organisational structures, were seen as poor candidates for DevOps adoption.
By 2016, that assumption had been overtaken by reality. Large, complex organisations — banks, retailers, insurers, and government agencies — were not merely following the trail blazed by startups. In many cases they were advancing DevOps practices in ways that smaller companies could not, precisely because the problems they solved were harder: mainframe integration, compliance pipelines, regulated release processes, and multi-team coordination at scale.
What DOES16 Revealed About Enterprise DevOps Maturity
The DevOps Enterprise Summit has always focused on practitioners inside large organisations rather than on vendors or tools. DOES16 continued that tradition, surfacing several themes that reflected the state of enterprise DevOps in late 2016:
- Leadership alignment matters as much as tooling. Presenters consistently pointed to executive sponsorship and cross-functional leadership as prerequisites for sustainable DevOps transformation, not optional extras.
- Value stream mapping went mainstream. Enterprises were using value stream mapping to surface bottlenecks in software delivery — often discovering that the slowest parts of the pipeline had nothing to do with code and everything to do with approval gates and handoffs.
- The “us vs. them” narrative was fading. Development, operations, security, and compliance teams were increasingly framing their work around shared outcomes rather than departmental boundaries.
- Metrics moved beyond deployment frequency. While the four key metrics popularised by research such as the State of DevOps Report (deployment frequency, lead time, mean time to restore, and change failure rate) were widely referenced, mature organisations were beginning to connect delivery metrics to business outcomes.
- Scaling DevOps remained the hardest problem. Organisations that had succeeded in one team or one product line were wrestling with how to replicate that success across hundreds of teams without mandating a single prescriptive process.
Key Trends Shaping Enterprise DevOps in 2016 and Beyond
Continuous Delivery at Enterprise Scale
Continuous delivery pipelines were no longer the exclusive domain of cloud-native startups. Enterprises were investing heavily in pipeline automation, with release orchestration emerging as a distinct discipline — coordinating deployments across dozens of interdependent services, environments, and teams in a controlled and auditable way.
Cultural Transformation as a Technical Problem
One of the more striking shifts visible at DOES16 was the willingness of enterprise speakers to discuss organisational change in concrete, engineering terms: reducing batch sizes, shortening feedback loops, making work visible. Cultural change was increasingly being treated not as a soft, aspirational goal but as a system design challenge with measurable outputs.
Security and Compliance Integration
DevSecOps — integrating security practices directly into the delivery pipeline — was gaining traction. Rather than treating security review as a late-stage gate, leading enterprises were embedding automated security scanning, policy as code, and compliance checks earlier in the pipeline to catch issues without slowing delivery.
The Role of Release Orchestration
Electric Cloud, the publisher of the original article, were advocates of release orchestration as a practice distinct from simple CI/CD automation. For enterprises managing complex, multi-team deployments, orchestrating releases across heterogeneous environments — including mainframes, on-premises infrastructure, and cloud — was a genuine operational challenge that point-to-point pipeline tools did not fully address.
Why Enterprise DevOps Progress Matters
The significance of large enterprises leading DevOps innovation extends beyond any individual organisation. Enterprises operate at a scale and under constraints — regulatory, financial, reputational — that startups do not. When a major bank or a healthcare provider successfully implements continuous delivery, it demonstrates that DevOps is not a niche practice for companies that can afford to move fast and break things. It proves that disciplined, safe, and rapid software delivery is achievable inside some of the most constrained operating environments in the world.
That proof point accelerates adoption across entire industries and changes the conversation with regulators and auditors who had previously viewed agile delivery as incompatible with governance requirements.
Original Source
This article summarises themes from the Electric Cloud blog post published in November 2016: DOES16 San Francisco: The Future of DevOps in the Enterprise – Trends & Predictions. Electric Cloud (now part of CloudBees) specialised in release automation and orchestration for enterprise software delivery.