Today DevOps Research and Assessment announced that they are launching the 2018 Accelerate State of DevOps Survey in collaboration with Google Cloud.
Our DevOps Product Manager, Ed Pearson (@edwardpearson), shares his thoughts on what this might bring.
If you’re not familiar with the State of DevOps Report, this annual survey and report has more than 27,000 responses and has done more than any other publication to help establish a picture of DevOps capabilities within organisations across the globe. This year’s report promises to dive even deeper into six key areas including; IaaS and PaaS, Monitoring and Observability, Databases, Testing, Workflow, Culture, Security, Reliability (read more here).
Here’s what I’m looking forward to reading more about in the State of DevOps Report 2018:
1 – Databases.
It’s hard not to agree that despite the work of a number of vendors, databases (and data!) have long been the poor relation in terms of both automation and testing. We repeatedly see organisations struggling to bring their database teams and developers on the DevOps ‘journey’ and it’ll be interesting to see how this sits with the rest of the industry – especially with the high performers.
2 – Workflow.
Specifically, the survey will be looking into how to ‘review change approvals to improve work’. Many people have written about how it’s time to kill the CAB. The State of DevOps report has been telling us that a lightweight change approval process, based on peer review results, reduces change fail rate for a number of years. Despite this evidence, moving away from the CAB is still something more traditional enterprises struggle with (in our experience). It’ll be interesting to see what we learn from this year’s report and whether it offers any insights on how traditional practices such as ITIL fit into this new world and how teams are managing security and regulatory requirements at this new pace.
3 – Culture.
I’m especially interested to see what we can learn about how leadership behaviours impact feelings of trust in teams. We know from research carried out at Google how important it is to have psychological safety within teams and no-one is underestimating the role of leaders in driving change. Many Agile-focused conferences through 2017 had talks that touched this, and it will be good to see what more we can learn from this year’s research about the impact of leaders on psychological safety.
What are you most interested in finding out from the survey? Let us know on Twitter.