DevOps Resource: Thinking Environments

Brought to you by the DevOps Enterprise Forum

Brought to you by the DevOps Enterprise Forum

Thinking Environments

Evaluating Organizational Models for DevOps to Accelerate Business and Empower Workers

While the traditional IT organization is structured into functional silos, DevOps relies on empowered, cross-functional teams. Is it possible to blend the two approaches and work within the traditional structure? Or do you need to restructure your organization to support DevOps?

In this resource we address these questions, identify models that enterprises and organizations are currently using, and propose ideas that can help leaders as they approach organization with DevOps in mind. 

What's Inside

SECTION 1

Why Does Organizational Structure Matter?

We begin this section by discussing the history of modern organizational design. Then, we compare and contrast the characteristics of a traditional functional silo model and a DevOps organization.

SECTION 2

Four Representative Models

We have identified four representative models, based on our discussions with a number of large organizations that have implemented DevOps approaches. The four modules we discuss are: Model 1—Traditional Functional Silo Model, Model 2— Matrix Mode, Model 3— Product And Platform Model, Model X— Adaptive Organization.

SECTION 3

In-Depth View of Models 

For each model, we identify its advantages and disadvantages for supporting DevOps, and we provide suggestions on how to make the most of the model. We also identify steps for transitioning from the model to higher maturity structures. 

The Four Organizational Models

Model 1—Traditional Functional Silo Model Key Characteristic: Clear single points of accountability for the quality of the individual functions, but accountability for cross-cutting concerns is only at the top (CIO) level.

Model 2— Matrix Mode Key Characteristic: This model uses a matrixed organization style, where accountability is owned by more than one reporting group. 

Model 3— Product and Platform Model Key Characteristic: Teams are formed around products as de ned by the perspective of the business. 

Model X— Adaptive Organization Key Characteristic: Model X is a much rarer species of organization and more than anything represents a glimpse into a future-state model that lies “beyond” contemporary organizational practices and thinking. 

What is the DevOps Enterprise Forum?

"Every year, more than 50 technology leaders and thinkers gather for three days to create written guidance on the best-known methods for overcoming the top obstacles in the DevOps Enterprise community."

Gene Kim Founder, IT Revolution 


Authors of This Resource

Mark Schwartz Enterprise Strategist, Amazon Web Services

Jason Cox Director, Systems Engineering, The Walt Disney Company

Jonathan Snyder Sr. Manager, Problem Management, Adobe Systems

Mark Rendell APAC DevOps and Agile Lead, Accenture

Chivas Nambiar Director DevOps Platform Engineering, Verizon

Mustafa Kapadia Digital Transformation & DevOps Service Line Leader, IBM

Authors of This Resource

Mark Schwartz Enterprise Strategist, Amazon Web Services

Jason Cox Director, Systems Engineering, The Walt Disney Company

Jonathan Snyder Sr. Manager, Problem Management, Adobe Systems

Mark Rendell Principal Director, Accenture

Chivas Nambiar Director DevOps Platform Engineering, Verizon

Mustafa Kapadia Digital Transformation & DevOps Service Line Leader, IBM

Get Access to all the DevOps Enterprise Forum Resources

When you download this DevOps Resource, we'll also send you new ones released each week authored by industry-leading DevOps practitioners.