If you do not feel you have a good handle on all the ways DevOps can benefit your enterprise and bring positive return on investment, you are not alone. While the concept of DevOps dates far back to 2009 (prehistoric times in our world!), the evolution and implementation of the procedures and tools that facilitate its use are still evolving. As has been discussed countless times - DevOps is not something you buy, it is something you do. And in order to 'do DevOps' you need to connect it to your business in a meaningful way to ensure long-term success. But let's pretend for a moment (shouldn't be hard to imagine) that your non-technical resources / upper-level management is holding out on making any changes that bring you closer to the DevOps principles of collaboration, culture and communication. How do you get them to invest in DevOps in your enterprise?
Stats for Doubters
If you are one of those who believe that accurate and unbiased statistics should be part of any basis for decision-making, we have some impressive Traditional Ops teams vs. DevOps teams for similarly sized companies:
- Traditional Ops are 41% more time-consuming overall
- Traditional Ops spends an average of 7.2 hours weekly on communication while
- Traditional Ops spends 21% more time putting out fires
- DevOps spends 33% more time on infrastructure improvements
- DevOps spends 60% less time handling support cases
Those should have gained your attention. For anyone still harboring uncertainty, here are some additional DevOps statistics to take you over the top regarding organizations that implement DevOps:
- 63% experience improvement in the quality of their software deployments
- 63% release new software more frequently
- 55% notice improved cooperation and collaboration
- 38% report a higher quality of code production
The implementation of a DevOps culture into any organization requires an updated approach to the ways that organizations process data. Rather than having development teams deliver software to operations that invariably returns it for repair after field-testing, both teams collaborate from the beginning. The result is a straight line from start to finish as opposed to arcs and zigzags displayed on traditional ops charts.
“Too often, these teams code themselves into a corner with mountains of proprietary scripts that actually add more waste to the system, instead of removing waste from the system, which is what the driving forces behind the DevOps movement are all about.”
– Mike Kavis, Cloud Technology Partners
When you think of DevOps in those terms, it is hard to justify traditional systems. DevOps simply makes good sense since it minimizes traditional kinks inherent with primitive approaches.