DevOps Changes and Trends of 2018

Dan Holloran October 08, 2018

DevOps
DevOps Changes and Trends of 2018 Blog Banner

Teams have been adopting the philosophies of DevOps since before it became a widely used term. And with each passing year, DevOps principles become more refined and more organizations buy into the concept. Although DevOps isn’t one-dimensional–and takes many forms–there are a few core tenets adopted by every successful DevOps organization.

The path to DevOps is a story of ups and downs. You try one thing, it doesn’t work, you iterate on the process, and you improve. At its core–this is DevOps. Through tight-knit communication and improved visibility between IT and developers, you can continuously test, collaborate, and improve.

Due to the ever-changing nature of DevOps, we wanted to recap a few common discoveries, changes, and trends we noticed throughout 2018.

1. More DevOps Adoption

In DORA’s newest research from Accelerate: State of DevOps 2018: Strategies for a New Economy, 27% of people said they worked in a DevOps team. For comparison, only 16% of people in 2014 answered the same way. More teams continue to take on the process of deepening collaboration between IT, security, and development. As more companies adopt DevOps, we continue to learn more about its benefits and find more innovative ways of implementing it.

2. Visibility and Reporting Across All Teams

According to the Puppet + Splunk 2018 State of DevOps Report, “C-suite respondents were more likely to report that these practices [of DevOps] were in frequent use.” A breakdown in communication and lack of visibility into blockers at the C-suite can cause C-level executives to believe their DevOps efforts are more effective than they actually are.

To emphasize this point, the same Puppet + Splunk Report goes on to state that, “64 percent of C-suite respondents believe security teams are involved in technology design and deployment versus 39 percent at the team level.” Management, development, IT, and security teams can start looking for ways to improve collaboration by acknowledging these feelings across the organization.

It’s important to recognize the informational gap so that DevOps teams can build visibility into PI planning, deployments, and reporting. Open lines of communication between engineers, managers, and the broader team can help identify areas lacking visibility and any potential bottlenecks.

DevOps & The Incident Lifecycle

3. DevOps and DevSecOps Are One and the Same

The practice of true DevOps inherently benefits security. People in the industry continue to argue over the terms DevOps and DevSecOps–but they really mean the same thing. DevOps principles such as collaboration, automation, and transparency should translate into bolstered security. With DevOps and Agile software development integrated into the SDLC and the incident management lifecycle, teams will naturally be more proactive about reliability and security.

In a recent article from Engine Yard they go on to state, “As DevOps practices become more closely integrated into cloud security and lifecycle management, DevOps will become more proactive, adding security in the development cycle in anticipation of security issues rather in response to problems uncovered once a project is deployed.”

Teams are quickly realizing the advantages of DevOps when it comes to building services quickly, reliably, and securely.

4. More Diversity in DevOps

According to this JAXenter post:

  • 12% of people identified as female
  • Last year, only 6% of the respondents were women
  • 25% of the respondent’s teams are women
  • 6% percent of respondents said they have some kind of disability
  • 9% preferred not to respond when asked about disabilities
  • 4% did not specify their gender, and 1% identified as non-binary

It’s just a start, but increased diversity in DevOps will lead to more viewpoints and help teams continuously improve. It’s a great trend to see that more diverse groups of people and expertise are drawn toward the DevOps culture.

5. Larger Adoption of Open Source Software

Also stated in the JAXenter article mentioned above, “Open source software is 1.75 times more likely to be extensively used by the highest performers, who are also 1.5 times more likely to expand open source usage in the future.” Teams are using open source software more often in order to build faster and take advantage of existing code and services.

While this is great for speed, DevOps teams need to be careful that open source software doesn’t have detrimental effects on security or operations.

Conclusion

DevOps is evolving for the better. More teams are working to build tighter bonds between developers, IT operations, and security. Added personnel diversity, an acceptance of open source software, a focus on security and transparency, and an increase in overall DevOps adoption is driving the future of software development and IT.

Due to the increasing speed of software delivery, the rapid adoption of Agile practices and CI/CD, combined with the growing threats of cybersecurity, DevOps has never been more necessary. The implementation of DevOps across your entire organization will drive a culture of speed, reliability, and security.

In our free eBook, Build the Resilient Future Faster: Creating a Culture of Reliability, learn from our story to see how adopting DevOps will drive deeper collaboration and help you build better services.

Ready to get started?

Let us help you make on-call suck less.