Taking DevOps from isolated teams to scaling across an enterprise is a significant challenge for any business. According to the report, establishing a platform approach to software delivery helps organizations standardize and scale DevOps practices across more application development teams. While the platform model is a fairly new approach for enabling application teams, it can help achieve overarching DevOps goals: faster and easier delivery of better-quality, more secure software.
Even more revealing in the report was that self-service capabilities were seen at higher levels of DevOps evolution, when companies’ DevOps practices are more mature. More evolved organizations are almost twice as likely as mid-level organizations to have high usage of internal platforms with self-service capabilities. Linked to findings in Puppet’s 2018 State of DevOps report, the DevOps evolution model consists of five stages of DevOps adoption which show critical practices at each stage and the “how” to get from one stage to the next.
“The underlying structural changes that have occurred to get to the highest level of DevOps evolution have reduced complexity in the technology stack, automated away a lot of toil, and reduced handoffs between teams — all while building a high degree of trust. These are all the necessary components for building an internal platform that can deliver higher value for the organization,” said Alanna Brown, Senior Director of Developer Relations and author of the State of DevOps report. “For organizations that are not ready to make the leap to a self-service platform approach,addressing change management processes within your company can also help eliminate toil and speed up software delivery.”
The report also revealed four common approaches to change management based on approval processes, degree of automation and risk mitigation techniques. The four approaches — operationally mature, engineering-driven, governance focused and ad hoc — result in different levels of effectiveness and different performance outcomes. Orthodox approvals make the change management process less efficient. Firms with high orthodox approvals are nine times more likely to have high levels of inefficiency than firms with low orthodox approvals. Teams that automate and practice advanced risk mitigation believe that their change management process reduces risk and downtime while facilitating the rate of change the business needs.
"This year we were able to gather data in-depth on how change management practices correlate with organizational success. The highlights for me were clear evidence that by using CI and automation as the primary change management mechanism outcomes are better, and effectiveness is higher,” said Michael Stahnke, Vice President, Platform, CircleCI. “Surprisingly, teams that have good outcomes are likely to not be satisfied with their change management process. Likely because they strive for continuous improvement — particularly when compared to organizations practicing a more traditional change management approach."
Additional key findings of the survey, include: