Digital business is changing the competitive environment; the proliferation of startups created by highly qualified unemployed seniors and entrepreneurs, the increasing adoption of cloud which reduces IT cost and the Internet of Things substituting traditional services with digital services are forcing business lines (BL) to opt for new paradigms. Market responsiveness achieved through flexible IT environments is what they need; extending DevOps to competitive and revenue issues and establishing it as the foundation of IT operating models is what'll make IT organizations relevant. That's what enterprise DevOps is about.
Why DevOps Initiatives Struggle to Meet BL Expectations
Despite its accelerated adoption, DevOps remains either misunderstood or improperly implemented. Today's implementation approaches have several weaknesses:
- Market responsiveness confusion with application delivery acceleration
- DevOps confusion with automation tools
- CIOs' lack of IT transformation strategy
Market Responsiveness isn't About Speed but Timely Revenue
One of the reasons certain DevOps initiatives don't generate business benefits is, 90 percent of IT consultants misunderstand market responsiveness; they erroneously narrow it to the capacity to deliver software at the speed of light. Simply put, market responsiveness relates to the continuous and accelerated delivery of added-value services, the bottom line isn't speed but timely revenue.
In fact, what BLs expect from IT is a greater focus on added-value priorities and the ability to absorb unpredictable market turbulences; that fact is substantiated by Patrick Phillips, in a bombshell "IT must adapt or die" he alerts "Five years ago less than 25 percent of business leaders rated their IT function effective at delivering the capabilities they need. Today that number hasn't changed. IT functions have strived tirelessly to understand demand, set priorities, deliver effectively, and capture value, yet the results still disappoint."
Narrowing DevOps to Tools its Ignoring its Competitive Advantages
Another factor preventing business benefits is, most consultants confuse DevOps with application deployment infrastructure, they see it from the distorted lenses of application deployment automation tools.
The tool dimension is erroneously considered more important than any other value drivers such as market understanding, cross-functional collaboration as well as accelerated problem solving and decision making. Adam Jacob, early proponent of DevOps and co-founder of Chef the leading IT-automation firm is clear about it, "Fundamentally DevOps is about taking the behaviors and beliefs that draw us together as people, combining them with a deep understanding of our customer's needs, and using that knowledge better products." To read more...
Implementing DevOps is Transforming Your IT Organization to the New Style of IT
My advise to CIOs is, "Implement DevOps as a transformation of your IT organization and don't narrow it to a technology change initiative." Strictly speaking, DevOps is disruptive and 70 percent of its business benefits depend on how well non-technological impediments to revenue are eliminated.
As illustrated, Enterprise DevOps is changing today's IT service delivery paradigm, it's taking IT organizations to the so-called new style of IT. In addition to leveraging cloud solutions' benefits and forcing CIOs to consider value drivers like organizational efficiency and cross-functional collaboration, it places application delivery and customer experience at the heart of the CIO's strategy:
DevOps High-Level Architecture - from ITaaSNow
CDPs Accelerate the Delivery of Expected Value
The CDP is the technological piece consultants and vendors have been reducing DevOps to. Concretely speaking, it's a Platform-as-a-Service (PaaS) which leverages infrastructure as code (IAC) mechanisms to automate, therefore, accelerate three stages of the application development life cycle including:
- Continuous integration
- Quality assurance
Agile IT Operational Models Eliminate Impediments to Value
The operating model is the non-technological piece most experts and vendors have been ignoring. It's a set of principles clarifying the rules to accelerate problem solving and decision-making; business and IT practices as well as the roles needed to deliver added-value priorities; and governance structure implemented in the form of Change Advisory Board (CAB) putting together business and IT executives to assess priorities, keep IT staff focused on them and deliver executive leadership. The bottom line is to make the IT organization agile and responsive to market opportunities and turbulences.
Enterprise DevOps isn't the complex technology stacks promoted by vendors; it's a set of practices combining infrastructure as code mechanisms and organizational efficiency leveraged to equip BLs with the only asset they need to prosper in the digital economy: market responsiveness.
I can't agree more with Adam Jacob on this, "Today there is a noisy market in teaching people how to do DevOps, or in tools that enable DevOps. Vendor after vendor will tell you they have the magical solution to this difficult business problem."