There has long been a divide between development and operations teams. But recently, there has been a movement to break down these metaphorical walls and build bridges of shared accountability between the two functions.
With the emergence of roles like DevOps and Site Reliability Engineering (SRE), we are seeing the introduction of a more collaborative approach to delivering reliable software.
Still, in the heat of battle, when an application breaks and customers are feeling the burn, who is ultimately responsible for identifying and fixing the issue?
In our Dev vs. Ops: The State of Accountability report, we surveyed over 2,000 IT professionals representing a wide range of company sizes, industries and geographical locations to get a sense of how shared accountability affects the delivery of reliable software in a DevOps environment, and what are some of the top challenges teams face when it comes to building and maintaining quality applications.
Take a look at some of our key takeaways, and get the full report here!
1. DevOps is no longer just a buzzword, but is still not a household practice.
[easy-tweet tweet=”Survey Finding #1: Only 17% of IT professionals claim to have fully adopted DevOps” user=”overopshq” hashtags=”devops,survey” url=”http://bit.ly/2SJAkro” template=”lite”]
The majority of respondents said that DevOps is in their roadmap, but more than 82% of organizations have only partially adopted DevOps practices (or haven’t adopted any), and only 17% of respondents claimed to have fully adopted DevOps.
2. Too many organizations rely on their customers to report errors in their application(s).
[easy-tweet tweet=”Survey Finding #2: More than 50% of IT professionals rely on customers to report application issues” user=”overopshq” hashtags=”devops,survey” url=”http://bit.ly/2SJAkro” template=”lite”]
Despite heavy adoption of automation and DevOps tooling, more than half of respondents said they rely on customers to tell them about errors. They make up just a part of the more than 3 in 4 respondents that reported using manual processes to discover errors in production.
3. A lot of people are spending more than a full day each week just troubleshooting errors.
[easy-tweet tweet=”Survey Finding #3: 1 in 4 IT professionals reported spending at least one full work day per week (or more) troubleshooting errors” user=”overopshq” hashtags=”devops,survey” url=”http://bit.ly/2SJAkro” template=”lite”]
Though more than half of respondents named productivity as the primary way they measure team effectiveness, 1 in 4 respondents reported spending roughly one full work day per week (or more) troubleshooting errors. Another 42% of respondents spend between a half to a full day of their week troubleshooting.
One More Thing…
A key focus of our conclusions from the report surrounds the current state of DevOps adoption and how it affects the overall health and reliability of an application. DevOps is ultimately supposed to help teams overcome many challenges they face today, perhaps the most common one being the silos between dev and ops.
BUT, and that’s a big but… For teams that haven’t started the transition yet and for those that have started the transition but haven’t completed it, the road is paved with new stresses and challenges.
In our report, we discovered that DevOps transformation can greatly impact the reliability of applications, though perhaps not in the ways that you may think.
How does DevOps adoption affect the challenges that teams face? How does it shift the responsibility for maintaining app quality? How does it affect the amount of time that teams spend troubleshooting? Find out the answers to these questions and more in the Dev vs. Ops: The State of Accountability report.