This vendor-written piece has been edited by Executive Networks Media to eliminate product promotion, but readers should note it will likely favour the submitter's approach.
Richard Gerdis, vice president, DevOps, Asia Pacific & Japan, CA Technologies
Root of All Problems
Today, a conflict exists within IT departments with agile developers wanting regular software deployments at a fast pace and operations teams prioritizing stability. Different success metrics for both the Dev and Ops teams leads to a situation where each team has its own objective. Lack of communication between the two teams can further complicate matters with developers unaware of the target environment and the operations team having no knowledge what the development team does.
Whatever the scenario, it does illustrate the technical face-off confronting many organizations today. In the IT corner, operations have the burden of maintaining stability over a complex mix of systems infrastructure, so there's no surprise that risk avoidance is the preferred method. While in the other corner, developers equipped with cloud-based automation tools now have the means (if we let them) to bypass the operations obstacles completely.
Confront the Problem Head-On
It could be argued that stability over throughput is an acceptable and necessary trade-off if the limitations we impose through process and standardization actually increase operational performance-leading to better business outcomes. But don't be fooled by rigid processes. Evidence suggests that speed and quality are not mutually exclusive-as highlighted in a new global study, commissioned by CA Technologies titled - Assembling the DevOps Jigsaw.
As per the findings, a majority of 69 percent of organizations in the Asia Pacific and Japan (APJ) region have implemented a DevOps approach, a swift jump from 20 percent last year. 15 percent of these DevOps practitioners have already reached advanced levels of adoption.
Advanced DevOps adopters were more likely to report that their digital initiatives contributed to competitiveness, customer retention and top- and bottom-line results. Across the globe, organizations with DevOps maturity were twice as likely to have seen a positive impact on revenue growth and 2.4 times more likely to have experienced higher profit growth.
In APJ, as compared to those without DevOps, advanced DevOps adopters were:
- 2.2 times more likely to have seen improvements in customer retention
- 2 times more likely to have seen improvements in customer acquisition
- 3 times more likely to have seen progress on market share
- 2.3 times more likely to have seen improvements in customer profitability
- 2.2 times more likely to have seen new income streams
Understanding DevOps- Strike the Right Balance
Maintaining balance means eliminating anything that prevents IT operating in its true natural state-a state of driving continuous business innovation from the rapid introduction of high quality software.
Operational rigidity and standardization can counter these goals and should be scrutinized-but it doesn't end there. In project and development phases, demands for more speeds and feeds (along with most of the funding) often result in application designs optimized for faster delivery, but at the expense of everything else. The result? There are more systems that are harder to maintain and support, which only increases the cost pressure on IT operations. Of course, this only gets worse when developers are incentivized on throughput and are never held accountable for to the overall disorder.
To bring balance and revert IT to its natural order, the cross-functional teams must put aside their differences and embrace DevOps. For operations, this means stepping out from behind the production curtain to help development bake quality into applications-especially as they are being developed, tested and deployed. For development, this means putting ego aside and accepting that because resilience, maintainability, scalability and security are not always top-of-mind, you will need help incorporating these elements. It also means everyone placing themselves in the shoes of the customer, building applications that are easier to support.
Sign up for Computerworld eNewsletters.