Not a Tech Pro Research member? Sign up for a Free Trial and get access to this content and more for one week.
IT leader’s guide to making DevOps work
- Originally Published:
- Oct 2016
More and more organizations are jumping on the DevOps bandwagon and benefiting from increased productivity and a smoother workflow. This ebook looks at how you can get the most from the DevOps approach.
From the ebook:
DevOps emphasizes the importance of communication and collaboration between software developers and production IT professionals, while automating the deployment of software and infrastructure changes.
The goal of DevOps is to create a working environment in which building, testing, and deploying software can occur rapidly, frequently, and reliably. In turn, this enables an organization to achieve its goals more quickly, allowing for a faster turnaround time in the deployment of new features, security patches, and bug fixes.
DevOps encompasses the already popular programming concepts of agile development, continuous integration, and continuous delivery and extends that ethos into the social aspect of IT by placing a premium on the importance of tearing down walls that divide development, operations, support, and management teams. To put it simply, DevOps makes the entire software lifecycle faster, from code commit to production deployment.
In the same vein, DevOps is a descriptive—not a prescriptive—concept. There is no single product or silver bullet that can fix existing problems in an organization; the purpose of DevOps is to increase collaboration.
A survey of 4,600 IT professionals by Puppet in June 2016 found that IT departments with a robust DevOps workflow deploy software 200 times more frequently than low-performing IT departments. In addition, they have 24 times faster recovery times, and three times lower rates of change failure, while spending 50% less time overall addressing security issues, and 22% less time on unplanned work.
While the concept of continuous delivery—and by extension, DevOps—may be counterintuitive to some, the end goal of frequent software deployments is to make the process so routine as to be a non-event, as opposed to a disruptive major rollout.
Already a member? Log in here