Welcome!

Blog Feed Post

The business case for Devops

Business case for Devops is a tricky subject.

This requires we clearly define the investment and then prove that the return on it is going to be positive.

So, what exactly is a Devops investment and how can we go about calculating its return?

At the most basic level organizations want their Dev and Ops team to effectively collaborate to ensure that they reach a  state of continuous delivery. Continuous is off course contextual. Continuous can be monthly, weekly or even hourly for  some organizations. Moreover, not all systems need continuous releases - the so called systems of records need lesser cadence than their new age counterparts - the systems of engagement which evolve more rapidly.

Continuous delivery is also not just about frequency. The underlying premise is that the increased speed will be achieved at less cost (more efficient automated process) with predictable quality (functionally and structurally).

So, in a way, Devops is just a 'means' towards the larger 'end' of continuous delivery. I prefer to use the word  predictable delivery instead of continuous delivery - which means that business pulls value as and when it needs with  predictable consistency rather than being continuously fed. 

With this definition in place, let's now first see how we calculate the return on a Devops investment. This is  important as unless the benefits are clear, investments would be difficult to justify.


As per the last Standish Report in 2012 (the next one is due in 2014), only 39% of IT projects succeed - 43% are  challenged (late, over budget, and/or with less than the required features and functions) and 18% outright fail (cancelled
prior to completion or delivered and never used). While the same statistics for 'smaller' projects is much better (and  incidentally as per Standish small projects need not necessarily mean 'agile' projects - small waterfall projects are  almost equally successful - we'll revisit this in more detail in a later post), it is not very difficult for organizations
to take stock of their fairly large portfolio of badly performing projects and calculate the 'return' if something was  done to improve their probability of success.


What I am implying is that Devops practices will improve the success rates of IT projects.
Agile has done its bit but its influence starts waning as a project enters its system testing stage. One way of looking  at Devops is to see it as an extension of Agile - into the last mile stages of an IT project and beyond. 

Interestingly in their 2013 CHAOS Manifesto, the Standish Group credits agile process with only a 10% influence on the  success of a small IT project (which is a project with less than $1M of labour content). Executive management support  (20%), project management expertise (12%) besides 3 other factors have more influence than 'agile'. In my view, Devops,  when properly institutionalized, can enhance the relative influence of agile processes from its current 10%.

So to summarize, the return of a Devops initiative should be improved IT projects performance.

Now let's turn to the other side of the equation - the 'investments'. What do organization's need to do to 'Devops' enable their IT teams?

In my view the investments can be bucketed under 3 broad categories:

Structure & Process

An empowered group has to be set up to investigate what structural changes are required to incentivize Dev and Ops to  collaborate.

One simple step could be to extend the scope of a 'project' to also include deployment and post live ops support for  atleast 6 months. Selected members of the Ops team become part of project teams (not just lent resources but owned  resources) which lasts for a significant duration after the system has gone live. This ensures that the Dev team can no 
longer just toss over the code to the Ops guys to run - they are equally responsible to run it themselves.


In fact, many organizations are extending this ownership beyond the 'stabilization' phase. They are repositioning their  'project teams' into 'product teams' with almost cradle to grave ownership for the assigned products / systems. This has  its own pros and cons but that’s the subject of another post some other day.

The other alternative could be a more formal alignment of responsibility and KRAs of the Dev and Ops team - joint ownership  of system upgradation and stability, common KRAs, etc.

The group has to find out what works best in their organizational context - by collecting / analyzing data, talking to  people and exploring best practices outside their organization. Not a very huge investment in terms of cost - maybe 4  people working for 4 weeks max - total 4 person months.

Technology

While all the 4 functional areas - planning / monitoring, building / integration, testing / validation and release /  deployment - lend themselves to technology enablement, organizations need to assess what their relative technology  strengths are in each of these areas and then define their investment strategy. 

While quality needs to be built it, probably the last stage when it should be formally validated is during the build  process. Automated unit test scripts should be integrated into the build process especially when integration is  continuous. Structural code checkers like CAST and specialist CI tools like Jenkins / Hudson add more teeth to this  process - although the same can be accomplished through multiple other tools.

Continuous testing needs rapid provisioning of testing environment and rapid deployment of builds / packages into the  provisioned environment. The provisioned test environment should also closely resemble the production environment - this  requires service virtualization capabilities (GreenHat, Lisa, etc.,) as well as a robust change & configuration management of production environments. The whole concept of 'infrastructure as code' where an entire environment can be mapped to a  piece of code and managed as any other CI enables this very easily. Rule based workflow enabled automated deployment of 
code through release automation tools like uDeploy, Nolio, Automic etc., coupled with server / cloud provisioning tools  like Chef / Puppet can be useful if implemented in the right context.


Devops is also about end to end flow so it is necessary that all the siloed sources of truth - project management,  requirements management, code management, test / defect management, service management are integrated and mapped to each  other to create one source of truth which can be viewed from different perspectives. Integration of tools is a major and  important investment in a Devops initiative. The ability to trace relationships between different entities - code -> user  story -> feature -> business process -> commit -> build -> package -> defect - > environment - > incident - > CR is  crucial. ALM platforms which accommodate integration with multiple tools like TeamForge, Jazz, Omnibus, etc., are almost a necessity.

Drive Change

This is the most difficult part.

More so because IT organizations won't have the luxury of taking a 'shut down' to transition to this new state of  collaboration. The tires of the car have to be changed while it is running.
It is not only difficult to achieve it, but also to estimate the efforts behind it.

Gene Kim's 'The Phoenix Project' clearly shows how daunting and complex this change exercise can be. It requires very  strong leadership and a multiple of other factors in the right proportions - sense of urgency, availability of skills,  technology literacy, culture of process rigor and an eco system which celebrates teamwork. If this right mix does not 
exist, it has to be created.


While the structure re-alignment and a formal 'process design' phase to define the new way of working will be a good  start, unless there is an urge to adopt this new mantra from that critical mass of people, it won't last. Investments have to be made in terms of identifying a change leader, change champions at various levels, trainings / workshops / awareness 
sessions / pep talks / a holistic communication campaign / forums participation, etc., to drive home the point that the  entire IT function has to perform this delicate balancing act of maintaining stability in the face of disruptive  innovation. That it is no longer Ops which is responsible for stability and Dev has the eternal prerogative of breaking  that stability under the guise of innovation - rather it is a collective mandate to deliver both.


In my experience, most organizations in their current Devops journey are paying far more attention to the 'Technology'  investment bucket relative to the other two. My hope is that this post will remind them that no transformation can be just about technology - it is always about people and the structural framework within which they interact with each other.

Read the original blog entry...

More Stories By Sujoy Sen

Sujoy is a TOGAF Certified Enterprise Architect, a Certified Six Sigma Black Belt and Manager of Organizational Excellence from American Society for Quality, a PMP, a CISA, an Agile Coach, a Devops Evangelist and lately, a Digital enthusiast. With over 20 years of professional experience now, he has led multiple consulting engagements with Fortune 500 customers across the globe. He has a Masters Degree in Quality Management and a Bachelors in Electrical Engineering. He is based out of New Jersey.

Latest Stories
DX World EXPO, LLC, a Lighthouse Point, Florida-based startup trade show producer and the creator of "DXWorldEXPO® - Digital Transformation Conference & Expo" has announced its executive management team. The team is headed by Levent Selamoglu, who has been named CEO. "Now is the time for a truly global DX event, to bring together the leading minds from the technology world in a conversation about Digital Transformation," he said in making the announcement.
"Space Monkey by Vivent Smart Home is a product that is a distributed cloud-based edge storage network. Vivent Smart Home, our parent company, is a smart home provider that places a lot of hard drives across homes in North America," explained JT Olds, Director of Engineering, and Brandon Crowfeather, Product Manager, at Vivint Smart Home, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
SYS-CON Events announced today that Conference Guru has been named “Media Sponsor” of the 22nd International Cloud Expo, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. A valuable conference experience generates new contacts, sales leads, potential strategic partners and potential investors; helps gather competitive intelligence and even provides inspiration for new products and services. Conference Guru works with conference organizers to pass great deals to gre...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
The Internet of Things will challenge the status quo of how IT and development organizations operate. Or will it? Certainly the fog layer of IoT requires special insights about data ontology, security and transactional integrity. But the developmental challenges are the same: People, Process and Platform. In his session at @ThingsExpo, Craig Sproule, CEO of Metavine, demonstrated how to move beyond today's coding paradigm and shared the must-have mindsets for removing complexity from the develop...
In his Opening Keynote at 21st Cloud Expo, John Considine, General Manager of IBM Cloud Infrastructure, led attendees through the exciting evolution of the cloud. He looked at this major disruption from the perspective of technology, business models, and what this means for enterprises of all sizes. John Considine is General Manager of Cloud Infrastructure Services at IBM. In that role he is responsible for leading IBM’s public cloud infrastructure including strategy, development, and offering m...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
Companies are harnessing data in ways we once associated with science fiction. Analysts have access to a plethora of visualization and reporting tools, but considering the vast amount of data businesses collect and limitations of CPUs, end users are forced to design their structures and systems with limitations. Until now. As the cloud toolkit to analyze data has evolved, GPUs have stepped in to massively parallel SQL, visualization and machine learning.
"Evatronix provides design services to companies that need to integrate the IoT technology in their products but they don't necessarily have the expertise, knowledge and design team to do so," explained Adam Morawiec, VP of Business Development at Evatronix, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
To get the most out of their data, successful companies are not focusing on queries and data lakes, they are actively integrating analytics into their operations with a data-first application development approach. Real-time adjustments to improve revenues, reduce costs, or mitigate risk rely on applications that minimize latency on a variety of data sources. In his session at @BigDataExpo, Jack Norris, Senior Vice President, Data and Applications at MapR Technologies, reviewed best practices to ...
Widespread fragmentation is stalling the growth of the IIoT and making it difficult for partners to work together. The number of software platforms, apps, hardware and connectivity standards is creating paralysis among businesses that are afraid of being locked into a solution. EdgeX Foundry is unifying the community around a common IoT edge framework and an ecosystem of interoperable components.
"ZeroStack is a startup in Silicon Valley. We're solving a very interesting problem around bringing public cloud convenience with private cloud control for enterprises and mid-size companies," explained Kamesh Pemmaraju, VP of Product Management at ZeroStack, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Large industrial manufacturing organizations are adopting the agile principles of cloud software companies. The industrial manufacturing development process has not scaled over time. Now that design CAD teams are geographically distributed, centralizing their work is key. With large multi-gigabyte projects, outdated tools have stifled industrial team agility, time-to-market milestones, and impacted P&L stakeholders.
"Akvelon is a software development company and we also provide consultancy services to folks who are looking to scale or accelerate their engineering roadmaps," explained Jeremiah Mothersell, Marketing Manager at Akvelon, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Enterprises are adopting Kubernetes to accelerate the development and the delivery of cloud-native applications. However, sharing a Kubernetes cluster between members of the same team can be challenging. And, sharing clusters across multiple teams is even harder. Kubernetes offers several constructs to help implement segmentation and isolation. However, these primitives can be complex to understand and apply. As a result, it’s becoming common for enterprises to end up with several clusters. Thi...