Dev vs. Ops: The State of Accountability – “The road to DevOps is paved with chaos”
More and more companies are making the transition to DevOps. However, they are finding accountability a struggle to understand and implement. We took a look at a report from OverOps about the state of accountability and what this means for DevOps pushing forward. Find out what teams are struggling with and avoid their mistakes!
OverOps interviewed 2,000 DevOps professionals about accountability and one thing is clear – wherever DevOps goes, chaos ensues.
Their findings have been published in their report: “Dev vs. Ops: The State of Accountability“. Let’s dive into the key findings and see how the DevOps world is changing, and what you can learn from these takeaways.
Accountability & taking responsibility
One of the key tenants of DevOps is the idea that both teams have an equal share of accountability. This road is not an easy path. Does this work in practice, or only in theory? Here’s how the respondents felt about team accountability.
- 73.0% agreed that Dev and Ops share responsibility for application quality. 66.9% believe that the whole team together shares responsibility when something goes wrong.
- What about their other quarter? 23.2% of respondents said that they feel a “lack of clarity” when it comes to who is responsible for errors in the code. Clearly, DevOps practices need to be clearer when addressing this issue so that 100% of team members can agree.
- This uncertainty leads to more errors. 23.2% replied that their lack of clarity is the “leading cause of errors making it into production”.
- Larger companies have more problems when it comes to role disorganization.
- Who is responsible for troubleshooting? 26.9% of Ops said that troubleshooting was not their responsibility, while only 8.0% of Developers said it was not their responsibility.
- Ensuring quality challenges is still a task in the making. 41.2% of respondents said that their company has “no formal process around ensuring reliability”. 11.4% of respondents must be very lucky; they replied that their team has no challenges.
“When everyone feels accountable, no one is really accountable”
OverOps, “Dev vs. Ops: The State of Accountability”
Moving at the speed of DevOps
No rest for the weary! DevOps is moving fast and causes chaos in its wake.
- Big companies love DevOps: According to the survey, the larger the company, the more likely they’ve adopted the DevOps workflow. Small companies are considering to adopt, but have not implemented it yet.
- Average release frequency: A very busy 14.4% of respondents replied that they release daily. Despite the fact that more than 90% of respondents deploy code at least once a month, “44.6% of respondents that have fully adopted DevOps say moving too quickly results in production errors”. Should quality be sacrificed for better speed?
- Top DevOps industries: Finance, telecom, healthcare, education, media & entertainment, energy, retail, public sector, technology, and manufacturing.
- Number one most popular developer tool: Automated testing tools
- Operations’ number one most popular tool: Infrastructure/network monitoring
- Plenty of bugs: 25.8% of respondents said that they spend more than 20% of their time troubleshooting.
- Not on the menu: 6.3% said they have no plans to adopt DevOps.
- Finding errors: Automation isn’t the future yet. 76.6% of respondents use at least one manual process in order to find errors, while 35.6% only use manual processes. What’s even more shocking is that 52.2% “reply on customers to tell them about errors”.
What did we learn?
How can you and your team benefit from these findings? Here are some pointers:
- Define your team members’ roles and responsibility.
- Take time to ensure quality before deploying.
- If your organization is large, it is much easier to fall into chaos. Ensure that everyone is on the same page and clarify project ownership with everyone involved.
- Don’t depend on users to report bugs to your team!
For the full report of their findings, download the report here.
“Dev vs. Ops: The State of Accountability” includes:
- DevOps demographics and infrastructure
- How do teams measure success?
- What sort of chaos is DevOps creating?
- Do developers an operators agree on the best tools?
- Challenges to overcome
Do these findings align with your own team? Did any of the data surprise you?