Puppet automation report is out: The significance of pervasive automation
From the principle of Getting Things Done, to DevOps and agile practices, automation is the number one word in everyone’s mouth. Here we take a look at the most interesting results of The Pervasive Automation Report by Puppet and how the picture of automation adoption among enterprises looks like.
Automation is the word in the mouth of those engaged in DevOps, those trying to realize the Getting Things Done principle etc.
One of the most prestigious reports in the IT world is out again and it’s all about automation. The Pervasive Automation Report by Puppet is rich in data and takes the pulse of what adoption rates, speed, and obstacles look like for enterprises.
But before we dig into the results, are you sure you know what “pervasive automation” actually means?
Pervasive automation is the concept of scaling automation broadly and deeply across the entire software delivery lifecycle.
Pervasive Automation Report
The significance of automation
Automation is seen as a competitive advantage by C-level executives, directors, managers, and individual contributors with slight discrepancies mostly on the across the different enterprise levels.
Legacy systems are the number one reason behind the obstacles enterprises face in their endeavors to implement software automation. This is mostly true from the individual contributors’ point of view!
Automated builds are difficult because we work with a lot of very old legacy code.
— QA analyst, participant in the Pervasive Automation Report
Interestingly enough, respondents depict enterprises to have achieved a significantly high level of automation throughout a number of processes.
When it comes to the different environments in which software is run, apart from a slight preference towards traditional environments among medium-sized enterprises, responses do not seem to differentiate that much. One point to notice, however, is that containerized environments are gaining momentum among the small enterprises.
Fast and successful enough?
In relation to the time needed for change deployment in the production of primary applications or services, the time period from one month to six months seems to be the most common case among all enterprise sizes. It is also interesting to notice that a significant percentage of large enterprises deploys change in the time period between one week and one month.
We all have this premise in our minds that release speed is the number one concern for an enterprise. But the results presented in the Puppet report seem to disagree! Quality of release seems to be the number one success factor for enterprises of all sizes, followed by customer satisfaction and release speed coming in third!
What comes next
As the Puppet report points out, pervasive automation is equal parts process, tooling, and culture, just like DevOps, and going further in its adoption is a collective endeavor and commitment.
But the road is not obstacle-free!
Much like any other automation principle, pervasive automation is to be challenged as new technologies are released, like cloud services, containers, and serverless computing.
The report argues that an absolute state of automation is close to impossible. The journey behind pervasive automation, however, is as close as we can get!