This article is based on analyst commentary originally published by CollabNet on blogs.collab.net in early 2017, reflecting on the state of DevOps and Application Lifecycle Management (ALM) at the close of 2016.
2016: A Turning Point for DevOps and ALM
By the end of 2016, DevOps had moved well beyond the realm of early adopters and enthusiast engineers. Enterprise teams across industries — including government — were visibly accelerating their transitions to Agile development practices and DevOps delivery models. To capture what really changed that year, CollabNet interviewed a panel of leading application development industry analysts, asking them a single pointed question:
“What were the greatest successes made in 2016 in the software development industry, specifically for ALM and DevOps?”
Their answers highlight four distinct but interconnected themes: toolchain maturity, operational adoption, CI/CD pipeline growth, and container standardization.
What the Analysts Said
Toolchain Cohesion: From Chaos to Collaboration
“DevOps/ALM coming of age. Rather than being a ragtag collection of disparate tools chosen and used by individuals for their own ends, we are finally seeing tools coming through that enable full collaboration and control along the entire lifecycle, while still enabling a degree of individual choice as to the base tools being used.”
Clive Longbottom, Founder and Analyst, Quocirca
Longbottom’s observation reflects a long-standing tension in DevOps tooling: individual teams often selected their own preferred tools — version control, build systems, testing frameworks, deployment platforms — without any unifying layer. By 2016, a new generation of ALM and DevOps platforms began offering integrated lifecycle views while preserving team autonomy at the tooling level. This balance between standardization and flexibility became a defining characteristic of more mature DevOps environments.
Operational Adoption: From Theory to Practice
“I think the biggest success in the industry is simply getting companies to understand the significant value, and in some cases, the need for tools to assist in DevOps. DevOps and Agile are more than just the frameworks and ideas for faster application development but should be the model for the operational usage of them. That shift toward implementing operational usage and the tools needed for it was very important.”
Edwin Yuen, Analyst, ESG
Yuen identifies a critical maturity milestone: the transition from understanding DevOps as a conceptual framework to actually instrumenting it operationally. Many organizations in earlier years adopted Agile ceremonies or DevOps language without putting the supporting tooling and processes in place. 2016 saw a meaningful shift toward organizations investing in the concrete infrastructure — pipelines, automation, monitoring — needed to operationalize these practices at scale.
CI/CD Maturity: Automation Becomes the New Normal
“In application development and deployment, DevOps is now the new normal. Surveys are showing that virtually all enterprises practice Agile to some degree. The growing maturity of CI/CD products means that enterprises will be able to see higher levels of automation in the pipeline, faster time to value, higher levels of software quality, and increased IT productivity.”
Stephen Hendrick, AD Research
Hendrick’s framing — “DevOps is now the new normal” — encapsulates a significant cultural and organizational shift. Continuous Integration and Continuous Delivery (CI/CD) tooling had by 2016 matured to the point where enterprises could realistically automate large portions of their build, test, and release pipelines. The downstream benefits Hendrick cites — faster time to value, improved quality, and higher IT productivity — are outcomes that well-implemented CI/CD pipelines demonstrably support, though actual gains depend heavily on organizational context and implementation quality.
Container Standardization: The Open Container Initiative
“Containers have been with us for awhile now. The issue has been portability and standardization. The Open Container Initiative Docker PoC and Release Candidates opened the door for industry standards around container formats, which will support greater portability in the ALM/DevOps space.”
Altaz Valani, Senior Research Director, Application Development Practice, InfoTech Research Group
Container technology — particularly Docker — had been gaining momentum for several years before 2016, but fragmentation around formats and runtime behavior remained a real concern for enterprise adoption. The Open Container Initiative (OCI), launched in 2015 under the Linux Foundation, made meaningful progress in 2016 toward defining open, vendor-neutral standards for container image formats and runtimes. This standardization effort was important for organizations looking to avoid lock-in and to build portable, reproducible delivery pipelines across development, staging, and production environments.
Key Themes Emerging from 2016
- Toolchain integration over tool proliferation: The industry moved toward platforms that could provide a unified view of the software delivery lifecycle without forcing teams to abandon their preferred tools entirely.
- Operational maturity: DevOps stopped being just a cultural talking point and became something organizations were actively instrumenting with real pipelines, automation, and feedback loops.
- CI/CD as baseline expectation: Continuous integration and delivery shifted from a competitive differentiator to a baseline expectation in enterprise software delivery.
- Container standardization: Industry-wide standards work, particularly through the OCI, began reducing the portability and interoperability friction that had slowed enterprise container adoption.
- Broader organizational buy-in: DevOps and Agile practices expanded beyond development teams to influence operations, and in some cases, wider organizational structures including government agencies.
What This Meant for 2017 and Beyond
The analyst consensus from the close of 2016 pointed clearly toward a future where DevOps toolchain integration, automated pipelines, and container-based delivery would become table stakes rather than advanced practice. Organizations that had not yet begun their DevOps journeys faced increasing competitive pressure, while those already on the path were focused on scaling their practices and eliminating remaining manual bottlenecks.
The challenges heading into 2017 — cultural resistance, toolchain sprawl, skills gaps, and the difficulty of scaling Agile practices in large enterprises — would prove to be the defining conversations of the years that followed. These themes remain relevant for any team still navigating its DevOps transformation today.
Original analyst commentary sourced from CollabNet (blogs.collab.net), published January 2017. Analyst affiliations reflect their roles at the time of the original publication.