The Governance Mismatch
October 23, 2017

Mark Schwartz
Amazon Web Services

DevOps poses a unique challenge and opportunity for IT governance. Traditionally we have governed IT in terms of projects. We lump a number of requirements, fulfilling a number of business needs, together into a bundle we call a project. We then build a business case for that project, put it through some governance process, perhaps an IT steering committee or some variation on one, to decide whether to allow it to proceed and to give it a place in the company's priorities. Once the project is ongoing, the team conducting it reports on its progress against its objectives, and probably against its planned costs and schedule, and some sort of oversight mechanism is in place to review, and perhaps act on, those results. You could say that our unit of governance is the "project," or that we govern at the granularity of the project. The project is a grouping of requirements, a thing that can be planned, an initiative that begins and ends.

Of course project-oriented governance lends itself to the Waterfall model. A fixed set of requirements; a plan; a Gantt chart; a well-defined series of phases; a result at the end – this is a natural way to treat a conglomeration of requirements that has an approved business case and a committed plan.

DevOps offers us a very different manner of execution. It is flow based, with new requirements being pulled into a pipeline, worked on, and deployed quickly to users: it optimizes the lead time for getting requirements into production by automating the delivery process and by eliminating handoffs between functional silos. Each individual requirement travels its own path to production, as if it were a packet making its way across the Internet. Our unit of execution is the individual user story or task, and with very frequent deployments, DevOps can reach single piece flow.

So we find ourselves in a position where we are governing at the project level yet executing at the individual requirement level – a somewhat disturbing mismatch. The consequence is that we are forced to hold requirements in inventory, so to speak, or plan in large batches of requirements.

In order to make a business case and present an adequately sized business proposal to the steering committee, we still need to assemble a large batch of requirements. In order to report on the status of – what? – something that can have a status, I suppose, we still report on the status of projects. We forego, in other words, the full benefits of DevOps – the ability to work leanly by reducing our batch size.

But how else can we govern? What exactly can a steering committee greenlight, and how does it know how that thing is progressing?

I'd like to suggest that the answer is simple and staring us in the face. Or rather, answers, because I believe there are two approaches. The first is to govern by business objectives. We determine a business objective that will have concrete business outcomes, preferably measurable ones. Then we make a business case – formal or informal – that therobjective is worth investing a particular amount of money in. If we decide that it is, we hand the objective to an empowered team and ask them to start accomplishing it – immediately. Because we are in a DevOps world, they should be able to begin deploying functionality virtually right away. We observe the business results they achieve, determine whether they are worth continued investment, and adjust our plans.

The second alternative is to govern IT investment the way we govern the rest of our company – without a governance process. The IT organization is allocated a budget and expected to make good decisions on how to spend it to accomplish the company's objectives. It is assessed and guided like any other part of the company – let's say that the CEO evaluates the CIO's performance and gives feedback to steer IT's direction. What is evaluated is the business outcome of the IT organization's decisions. The advantage of this approach is that it allows for continual transformation, continuous investments in systems, rather than the periodic, on-again-off-again flow of investment when we organize around projects.

It's one thing to reap operational advantages from DevOps. It is a different thing to maximize the value that DevOps can deliver to the enterprise, strategically as well as tactically. For that, we need to rethink governance.

Mark Schwartz, Enterprise Strategist at Amazon Web Services (AWS), is the Author of "A Seat at the Table"
Share this

Industry News

May 17, 2022

DevOps Institute, a global professional association for advancing the human elements of DevOps, announced the release of the Upskilling IT 2022 report.

May 17, 2022

Replicated announced a host of new platform features and capabilities that enable their customers to accelerate enterprise adoption of their Kubernetes applications.

May 17, 2022

Codefresh announced that its flagship continuous delivery (CD) platform will be made accessible as a fully-hosted solution for DevOps teams seeking to quickly and easily achieve frictionless, GitOps-based continuous software delivery in the cloud.

May 16, 2022

Red Hat announced new capabilities and enhancements across its portfolio of open hybrid cloud solutions aimed at accelerating enterprise adoption of edge compute architectures through the Red Hat Edge initiative.

May 16, 2022

D2iQ announced a partnership with GitLab.

May 16, 2022

Kasten by Veeam announced the new Kasten by Veeam K10 V5.0 Kubernetes data management platform.

May 12, 2022

Red Hat introduced Red Hat Enterprise Linux 9, the Linux operating system designed to drive more consistent innovation across the open hybrid cloud, from bare metal servers to cloud providers and the farthest edge of enterprise networks.

May 12, 2022

Couchbase announced version 7.1 of Couchbase Server.

May 12, 2022

Copado added Copado Robotic Testing to Copado Essentials.

May 11, 2022

Red Hat announced new advancements within its Red Hat Cloud Services portfolio, delivering a fully-managed and streamlined user experience as organizations build, deploy, manage and scale cloud-native applications across hybrid environments.

May 11, 2022

JFrog introduced a new Docker Desktop Extension for JFrog Xray that allows organizations to automatically scan Docker Containers for vulnerabilities and violations early in the development process.

May 11, 2022

Progress announced a series of updates in Progress Telerik and Progress Kendo UI.

May 11, 2022

Vultr announces that Vultr Kubernetes Engine (VKE) is generally available.

May 10, 2022

Docker announced new features and partnerships to increase developer productivity. Specifically, the company announced Docker Extensions which allow developers to discover and add complementary development tools to Docker Desktop.

May 10, 2022

Red Hat announced the general availability of Red Hat Ansible Automation Platform on Microsoft Azure, pairing hybrid cloud automation with the convenience and support of a managed offering.