9
ORGANIZATIONAL DESIGN FOR DEVOPS

DOES16 San Francisco - DevOps Workshop: Organizational Design

Embed Size (px)

Citation preview

Page 1: DOES16 San Francisco - DevOps Workshop: Organizational Design

ORGANIZATIONAL DESIGN FOR DEVOPS

Page 2: DOES16 San Francisco - DevOps Workshop: Organizational Design

ORGANIZATIONAL STRUCTURES

Model 1: Traditional Functional Silos

Model 2: Matrix Model 3: Product Model X: Adaptive

Page 3: DOES16 San Francisco - DevOps Workshop: Organizational Design

MODEL 1: FUNCTIONAL SILOS

Page 4: DOES16 San Francisco - DevOps Workshop: Organizational Design

MODEL 2A: MATRIX

Page 5: DOES16 San Francisco - DevOps Workshop: Organizational Design

MODEL 2B: MATRIXEMBEDDED FUNCTIONS

Page 6: DOES16 San Francisco - DevOps Workshop: Organizational Design

MODEL 3: PRODUCT

Page 7: DOES16 San Francisco - DevOps Workshop: Organizational Design

MODEL X: ADAPTIVE

Page 8: DOES16 San Francisco - DevOps Workshop: Organizational Design

SUMMARY EVALUATION

Model 1 Model 2 Model 3 Model X

Promotes DevOps, short lead times

Encourages collaboration and communication (silo defeat communication)

Right kind of accountability (get on the right queue), routing instructions)

Flat organization

Optimize the whole - deal with overall strategy, standards, etc.

Self-organizing overall structure - can it reconfigure itself easily?

Implements any necessary risk mitigation and compliance

Must fit into the rest of the organization

Page 9: DOES16 San Francisco - DevOps Workshop: Organizational Design

CONTRIBUTING AUTHORSMark Schwartz, CIO, US Citizenship and Immigration Services, [email protected]

Jason Cox, Director Systems Engineering, Disney,  [email protected], @jasonacox

Jonathan Snyder, Sr. Manager, Service Deployment & Quality, Adobe Systems, [email protected]

Mark Rendell, Principal Director, Accenture, [email protected], @markosrendell

Chivas Nambiar, Director Systems Engineering, Verizon, [email protected]

Mustafa Kapadia, NA DevOps Service Line Leader, IBM, [email protected]