DevOps.com

  • Latest
    • Articles
    • Features
    • Most Read
    • News
    • News Releases
  • Topics
    • AI
    • Continuous Delivery
    • Continuous Testing
    • Cloud
    • Culture
    • DevSecOps
    • Enterprise DevOps
    • Leadership Suite
    • DevOps Practice
    • ROELBOB
    • DevOps Toolbox
    • IT as Code
  • Videos/Podcasts
    • DevOps Chats
    • DevOps Unbound
  • Webinars
    • Upcoming
    • On-Demand Webinars
  • Library
  • Events
    • Upcoming Events
    • On-Demand Events
  • Sponsored Communities
    • AWS Community Hub
    • CloudBees
    • IT as Code
    • Rocket on DevOps.com
    • Traceable on DevOps.com
    • Quali on DevOps.com
  • Related Sites
    • Techstrong Group
    • Container Journal
    • Security Boulevard
    • Techstrong Research
    • DevOps Chat
    • DevOps Dozen
    • DevOps TV
    • Digital Anarchist
  • Media Kit
  • About
  • AI
  • Cloud
  • Continuous Delivery
  • Continuous Testing
  • DevSecOps
  • DevOps Onramp
  • Practices
  • ROELBOB
  • Low-Code/No-Code
  • IT as Code
  • More
    • Application Performance Management/Monitoring
    • Culture
    • Enterprise DevOps

Home » Blogs » Why Does DevOps Require A New Operating Model?

Why Does DevOps Require A New Operating Model?

By: Mustafa Kapadia on June 22, 2017 3 Comments

For many, redesigning the operating model is table stakes for a successful DevOps transformation. But have you ever wondered why? Popular wisdom will have you believe that the main reason for operating model redesign are to…

Recent Posts By Mustafa Kapadia
  • Are You a Product Team in Name Only?
  • What is an Agile IT Organization?
  • Transforming the Annual Budgeting Process For DevOps
More from Mustafa Kapadia
Related Posts
  • Why Does DevOps Require A New Operating Model?
  • DevOps Unbound EP 21 Leading a DevOps Transformation – Lessons Learned – TechStrong TV
  • DevOps Unbound EP 19 – How AI and ML are being used in DevOps Today – TechStrong TV
    Related Categories
  • Blogs
  • Business of DevOps
  • Leadership Suite
    Related Topics
  • Operating Model
  • Organization Change
  • Organization Redesign
Show more
Show less

“Improve collaboration between business and IT”
“Realign metrics”
“Take full advantage of the new tools”
“And even jump start culture change”

AppSec/API Security 2022

While these are all good reasons, frankly they miss the point. Experience suggests there is a more practical reason – match ownership with desired output.

What do we mean by that? Well first, lets look at how the current model works.

There a no real owners in IT

DevOps is about optimizing the flow of work across the Software Delivery Lifecycle. But who owns this end to end flow – idea conception to release? Who owns the cycle time? And who it responsible for improving it?

The short answer is everyone. Business, architects, and engineers own the planning phase. Developers own development and testing. Operators own releases. The PMO owns the project plan. And the business owns the funding.

And yes in theory all of these groups are supposed to get along. Unfortunately it rarely happens. Incentives and metrics force them to optimize their silos but not the overall flow. the current operating model encourages tribal siloed mentality. It’s the reason why finger pointing is elevated to an art form and “CYA” is your ticket to getting promoted.

One can argue that the CIO does own it all. But, in my humble opinion, CIOs have to tend to hundreds (if not thousands) of applications. Making it impossible for them to play an active role on a daily basis.

Which brings me back to my earlier point…having too many owners is just as good as having no owners. Rectifying this misalignment is the main reason why so many CIOs choose to change the operating model. Even when it may seem risky at the onset.

In fact many have found that fixing the ownership problem actually accelerates the DevOps transformation.

If you want to make dramatic progress create a single owner for each application

There are lots of names for this type of operating model. Some call it a product model, others call is squads, IBM calls it cell. But the essence is the same – for every application, create a single owner, that manages a cross functional team, has end to end authority, and is measured on business outputs.

This owner is responsible for the entire delivery lifecycle. They manage both the inputs (resources, process, tools, infrastructure etc.) and the outputs (business impact, features, time to market, quality, productivity etc.).

This does four things. First, managers that are the most familiar with the application and its users can now finally optimize the inputs in order to maximize the outputs. Second, by pushing authority to the front lines, you create a sense of true ownership. Pride (or shame) are powerful motivators for quality.

Third, by decoupling the teams you get rid of bureaucracy, give rise to friendly competition, and localize the risks. And fourth, the reason why most CIOs go through with the change despite the risks, it provides you with a one throat to choke.

You can, of course, continue to implement DevOps in the current operating model. But it’s almost impossible to overcome the operating model inertia. A move to a product model can actually accelerate your transformation. The model serves as a catalyst for the organization move past the “old way” of working in silos and create “new ways” of working with the flow.

Create your one throat to choke and see how quickly things change.

— Mustafa Kapadia

Filed Under: Blogs, Business of DevOps, Leadership Suite Tagged With: Operating Model, Organization Change, Organization Redesign

Sponsored Content
Featured eBook
The State of Open Source Vulnerabilities 2020

The State of Open Source Vulnerabilities 2020

Open source components have become an integral part of today’s software applications — it’s impossible to keep up with the hectic pace of release cycles without them. As open source usage continues to grow, so does the number of eyes focused on open source security research, resulting in a record-breaking ... Read More
« DevOps Chat: Design Thinking w/ Sarah Plantenberg, IBM
The Need for Recognition »

TechStrong TV – Live

Click full-screen to enable volume control
Watch latest episodes and shows

Upcoming Webinars

Code Tampering: Four Keys to Pipeline Integrity
Wednesday, August 17, 2022 - 1:00 pm EDT
The ROI of Integration: Must-Have Capabilities to Maximize Efficiency and Communication
Thursday, August 18, 2022 - 11:00 am EDT
Best Practices For Writing Secure Terraform
Thursday, August 18, 2022 - 3:00 pm EDT

Latest from DevOps.com

Contrast Security Adds API Support to Security Platform
August 16, 2022 | Mike Vizard
Avoiding Security Review Delays
August 16, 2022 | Waqas Nazir
Building a Platform for DevOps Evolution, Part One
August 16, 2022 | Bob Davis
Techstrong TV: Leveraging Low-Code Technology with Tools & Digital Transformation
August 15, 2022 | Mitch Ashley
Five Great DevOps Job Opportunities
August 15, 2022 | Mike Vizard

GET THE TOP STORIES OF THE WEEK

Download Free eBook

The Automated Enterprise
The Automated Enterprise

Most Read on DevOps.com

MLOps Vs. DevOps: What’s the Difference?
August 10, 2022 | Gilad David Maayan
We Must Kill ‘Dinosaur’ JavaScript | Microsoft Open Sources ...
August 11, 2022 | Richi Jennings
What GitHub’s 2FA Mandate Means for Devs Everywhere
August 11, 2022 | Doug Kersten
CloudNativeDay: WASM to Drive Next IT Epoch
August 10, 2022 | Mike Vizard
Next-Level Tech: DevOps Meets CSOps
August 12, 2022 | Jonathan Rende

On-Demand Webinars

DevOps.com Webinar ReplaysDevOps.com Webinar Replays
  • Home
  • About DevOps.com
  • Meet our Authors
  • Write for DevOps.com
  • Media Kit
  • Sponsor Info
  • Copyright
  • TOS
  • Privacy Policy

Powered by Techstrong Group, Inc.

© 2022 ·Techstrong Group, Inc.All rights reserved.