DevOps is rapidly emerging as the de facto way of developing, delivering and refining software, and not just at the usual suspects Uber, Google, Facebook et al. In the wider context technology is becoming integral to more and more aspects of life. As a business strategy this translates into 'digital transformation'. As an organisational philosophy it can be seen as part of the drive for continuous improvement. And at the level of the IT team it means Agile development and DevOps.
A few years back a new adage emerged: "every company is a software company now". As hardware becomes commoditised and technology's tendrils reach ever further into every product and service, the theory goes, software becomes the differentiator. For most organisations this means a shorter release cycle so they can adapt flexibly to changes in the market, with rapid iterations and frequent improvements - the logical outcome of which is that every company is becoming a DevOps company too.
DevOps is a journey in the course of which more and more physical, one-off and manual tasks are abstracted into code. Arguably this journey has no end: the DevOps engineers of today are really just the developers of tomorrow, and there will always be new tasks to be tied into a framework, coded and automated.
Recently, as part of our annual DevOps research, Computing polled about 200 IT professionals who had some involvement in software development, from those just beginning to those who felt they had reached maturity. The chart above shows just how rapidly DevOps as a practical concept is taking off. Since last year the biggest jump has been in the proportion of respondents 'learning the ropes' - up from 23 per cent to 35 per cent. Only nine percent were not considering it.
DevOps has broken out of the 'early adopter' phase and is now entering the mainstream. However, the proportion considering themselves to be 'advancing' or 'mature' is relatively unchanged. These early adopters who are now looking to scale up DevOps to the next stage.
On the whole, these early adopters showed a high degree of satisfaction with the outcome of their DevOps efforts so far. On a scale of one to seven with one being highly dissatisfied and seven being very satisfied, the mean of the responses was five or 'pretty happy'. The mode average was six out of seven - 38 per cent of respondents placed themselves there.
Half of the respondents were planning to scale up their DevOps activities in the next year. Only 22 per cent said that they would not. The remainder fell into the "maybe" or "not sure" camps.
In 2018 DevOps has become an enterprise concern
It would seem that the argument for DevOps has largely been won. It is certainly no longer considered a flash in the pan. In 2018 DevOps has become an enterprise concern, and there's no going back now.
But while it may be a product of the business environment this is not to say that DevOps is some sort of universal panacea. Like any new way of working it needs time to bed in and it's never going to please everybody all of the time. Nor will it be the only way the software is produced, being best suited to smaller, fast-changing applications.
DevOps (and more generally Agile) can sometimes be met with bewilderment on the part of the business or end users, particularly if they are used to receiving their software fully polished with all bells and whistles functional from the start. A barebones MVP delivered without explanation will seem like a step backwards.
While a certain amount of enthusiasm is vital to get the board interested enough to support DevOps, overplaying that hand can something backfire in the form of unrealistic expectations. Finally there can be friction within the IT department itself as the old roles are changed. However, Computing's research found a positive picture, with expectations being met overall.
The number saying that DevOps is nearly meeting most expectations has risen markedly since last year, even if at the top end the numbers fully meeting expectations have not increased and may even have fallen off slightly. This may be indicative of new companies coming on board with DevOps.
Where DevOps has not yet delivered as hoped, there may be a number of explanations.
"We still don't have a setup that delivers truly agile deployment. The DevOps behaviour still has to be fully embraced," said one person.
"They always want more, cheaper and faster," complained another, while one third spoke of a lack of training for staff.
So companies need to ensure that Agile ways of working start to pervade the organisation, not just the IT department. They also need to ensure that DevOps is communicated properly so that expectations are not set too high. And of course the need to ensure they have the right staff incentives and training set up.
Turn to next page
Rancher has big - and small - plans for the container orchestration platform
Testers have to be destroyers, argues Mark Wilson. But too often testers aren't trying too hard to bust the software. Rather, they are trying to show it working
Design is all about applying the fundamental principles of engineering, believes Mark Wilson, in the latest in his ten-part series
A method should lead a project to the desired result without significant variation, with much of the thinking already been done for you, writes Mark Wilson