Scaling Devops

59
http://thoughtworks-studios.com / Enterprise Devops Breaking Down the Barriers between Development and IT Operations November 9, 2011 Jez Humble, ThoughtWorks Studios @jezhumble #continuousdelivery http://continuousdelivery.com /

description

There's a recording of this talk from GOTO Aarhus 2011: http://www.infoq.com/presentations/Scaling-Devops Common issues when transforming IT organizations, and how devops addresses them.

Transcript of Scaling Devops

Page 1: Scaling Devops

http://thoughtworks-studios.com/

Enterprise DevopsBreaking Down the Barriers between Development and IT Operations

November 9, 2011

Jez Humble, ThoughtWorks Studios@jezhumble #continuousdeliveryhttp://continuousdelivery.com/

Page 2: Scaling Devops

business agility

“The main obstacles to improved business responsiveness are slow decision-making, conflicting departmental goals and priorities, risk-averse cultures and silo-based information.”

Economist Intelligence Unit: “Organisational agility:How business can survive and thrive in turbulent times”

Page 3: Scaling Devops

enterprise-class problems

• Political

• Organizational

• Project / program management

• Governance

Page 4: Scaling Devops

“the enterprise”

Project A

Project B

Project C

DBAs

Infrastructure team

Service desk

Value stream

OperationsEngineeringBusiness

Page 5: Scaling Devops

“the enterprise”

Project A

Project B

Project C

DBAs

Infrastructure team

Service desk

Value stream

OperationsEngineeringBusiness

Ping!

Page 6: Scaling Devops

enterprise politics

Project A

Project B

Project C

DBAs

Infrastructure team

Service desk

Let’s createa new

product

Value stream

OperationsEngineeringBusiness

Page 7: Scaling Devops

enterprise politics

Project A

Project B

Project C

DBAs

Infrastructure team

Service desk

Let’s createa new

product

Get offmy land!

Value stream

OperationsEngineeringBusiness

Page 8: Scaling Devops

Project A

Project B

Project C

DBAs

Infrastructure team

Service desk

Let’s createa new

product

enterprise projects

Value stream

OperationsEngineeringBusiness

Page 9: Scaling Devops

Project A

Project B

Project C

DBAs

Infrastructure team

Service desk

Let’s createa new

product

enterprise projects

Value stream

OperationsEngineeringBusiness

Page 10: Scaling Devops

Project A

Project B

Project C

DBAs

Infrastructure team

Service desk

Let’s createa new

product

enterprise projects

Value stream

OperationsEngineeringBusiness

Page 11: Scaling Devops

Project A

Project B

Project C

DBAs

Infrastructure team

Service desk

Ping!

Let’s createa new

product

enterprise projects

Value stream

OperationsEngineeringBusiness

Page 12: Scaling Devops

Project A

Project B

DBAs

Infrastructure team

Service desk

Ping!

Let’s createa new

product

enterprise projects

Value stream

OperationsEngineeringBusiness

Page 13: Scaling Devops

Project A

Project B

DBAs

Infrastructure team

Service desk

Ping!

Let’s createa new

product

enterprise projects

Value stream

OperationsEngineeringBusiness

Project D

Page 14: Scaling Devops

Project A

Project B

DBAs

Infrastructure team

Service desk

Project D

We’re going agile!

Value stream

OperationsEngineeringBusiness

Page 15: Scaling Devops

Project A

Project B

DBAs

Infrastructure team

Service desk

Project D

We’re going agile! Oh crap!Oh crap!

Value stream

OperationsEngineeringBusiness

Page 16: Scaling Devops

Project A

Project B

DBAs

Infrastructure team

Service desk

Value stream

OperationsEngineeringBusiness

Project D

Page 17: Scaling Devops

Project A

Project B

DBAs

Infrastructure team

Service desk

Value stream

OperationsEngineeringBusiness

Project D

Page 18: Scaling Devops

Project A

Project B

DBAs

Infrastructure team

Service desk

Value stream

OperationsEngineeringBusiness

Project D

Page 19: Scaling Devops

Project A

Project B

DBAs

Infrastructure team

Service desk

Value stream

OperationsEngineeringBusiness

Project D

Page 20: Scaling Devops

Project A

Project B

DBAs

Infrastructure team

Service desk

Value stream

OperationsEngineeringBusiness

Project D

Our test-driven code follows SOLID

principles

Page 21: Scaling Devops

Project A

Project B

DBAs

Infrastructure team

Service desk

Value stream

OperationsEngineeringBusiness

Project D

Our test-driven code follows SOLID

principles

Shame itdoesn’t work

Page 22: Scaling Devops

Project A

Project B

DBAs

Infrastructure team

Service desk

Value stream

OperationsEngineeringBusiness

Project D

Our test-driven code follows SOLID

principles

Shame itdoesn’t work

Changemanagement

Page 23: Scaling Devops

cultureautomation

measurementsharing

devops

Page 24: Scaling Devops

culture

• ops involved in inceptions, showcases, retrospectives

• devs go to weekly ops stand-ups

• devs rotate through ops

• devs carry pagers

• organize your incentives (Hawthorne e!ect)

Page 25: Scaling Devops

automation

• build, deploy, test release (deployment pipeline)

• provisioning & management of infrastructure and environments (infrastructure-as-code)

• database migrations and deployments

Page 26: Scaling Devops

measurement

• business metrics - revenue, # orders, # users

• ops metrics - changes, incidents, TTD, TTRS, TBF

• technical metrics - TPS, response time, hits

• root cause analysis - which changes break stu!?

Page 27: Scaling Devops

sharing

• celebrate success together (one team)

• knowledge

• tools and techniques (bdd, refactoring, continuous integration)

Page 28: Scaling Devops

Project A

Project B

Project C

DBAs

Infrastructure team

Service desk

Value stream

OperationsEngineeringBusiness

Page 29: Scaling Devops

developers write production-ready code

continuous delivery

Page 30: Scaling Devops

developers write production-ready code

everyone collaborates throughout lifecycle

continuous delivery

Page 31: Scaling Devops

faster feedback loops

developers write production-ready code

everyone collaborates throughout lifecycle

continuous delivery

Page 32: Scaling Devops

faster feedback loops

developers write production-ready code

everyone collaborates throughout lifecycle

lower-risk, more reliable releases

continuous delivery

Page 33: Scaling Devops

faster feedback loops

developers write production-ready code

everyone collaborates throughout lifecycle

done means released

lower-risk, more reliable releases

continuous delivery

Page 34: Scaling Devops

agile triangle

value(releasable product)

quality(reliable, adaptable product)

constraints(cost, schedule, scope)

Jim Highsmith: Agile Project Management

Page 35: Scaling Devops

do less

Far more than 50% of functionality in software is rarely or never used. These aren’t just marginally valued features; many are no-value features.

The Standish Group, reported in the IEEE conference 2002

Page 36: Scaling Devops

quality

“if we do not know who the customer is, we do not know what quality is”

the lean startup, ch. 6 - test

Page 37: Scaling Devops

build quality in

“Cease dependence on mass inspection to achieve quality. Improve the process and build quality into the product in the "rst place”

W. Edwards Deming

Page 38: Scaling Devops

ops still has all that legacy crap

but

Page 39: Scaling Devops

ops still has all that legacy crap

no way to rationally decide what to retire

but

Page 40: Scaling Devops

deciding what to do is command-and-control

ops still has all that legacy crap

no way to rationally decide what to retire

but

Page 41: Scaling Devops

deciding what to do is command-and-control

ops still has all that legacy crap

no way to rationally decide what to retire

people who can make the changes aren’t the ones feeling the pain

but

Page 42: Scaling Devops

You build it,You run it

werner vogels, cto, amazon

Page 43: Scaling Devops

Project A

Project B

Project C

DBAs

Infrastructure team

Service desk

Value stream

OperationsEngineeringBusiness

Treat these servicesas if they were products

Page 44: Scaling Devops

Service desk

Value stream

OperationsProducts / Services

Ping!

think product

IaaS

Ops management

Page 45: Scaling Devops

teams can measure cost and value delivered per product

therefore...

Page 46: Scaling Devops

teams can measure cost and value delivered per productteams can rationally determine what to prioritize in their product backlog

therefore...

Page 47: Scaling Devops

teams can self-manage using the lean startup methodology

teams can measure cost and value delivered per productteams can rationally determine what to prioritize in their product backlog

therefore...

Page 48: Scaling Devops

teams can self-manage using the lean startup methodology

teams can measure cost and value delivered per productteams can rationally determine what to prioritize in their product backlog

architecture group responsible for regulating and monitoring system-level attributes

therefore...

Page 49: Scaling Devops

teams can self-manage using the lean startup methodology

teams can measure cost and value delivered per productteams can rationally determine what to prioritize in their product backlog

PMO regulates and measures to prevent “market failure” and manage externalities

architecture group responsible for regulating and monitoring system-level attributes

therefore...

Page 50: Scaling Devops

architecture group

organizational change

Page 51: Scaling Devops

architecture group

PMO

organizational change

Page 52: Scaling Devops

operations

architecture group

PMO

organizational change

Page 53: Scaling Devops

operations

architecture group

PMO

business

organizational change

Page 54: Scaling Devops

risk management

enterprise governance

Page 55: Scaling Devops

risk management

SOX, ITIL, COBIT

enterprise governance

Page 56: Scaling Devops

segregation of duties

risk management

SOX, ITIL, COBIT

enterprise governance

Page 57: Scaling Devops

segregation of duties

risk management

SOX, ITIL, COBIT

change management

enterprise governance

Page 58: Scaling Devops

segregation of duties

risk management

SOX, ITIL, COBIT

auditing and compliance

change management

enterprise governance