Kill DevOps, Mark Smalley

Enterprise governance

of IT

Enterprise architecture

Business relationship

management

IT service management

Business analysis

Project management

Agile /DevOps

Business information

management

Application management

Building bridges

• Yet another hype

• Kill DevOps!

Storyline

• Yet another hype

• Define DevOps

• Kill DevOps!

Storyline

• Yet another hype

• Define DevOps

• Expand DevOps

• Kill DevOps!

Storyline

• Yet another hype

• Define DevOps

• Expand DevOps

• Sell DevOps

• Kill DevOps!

Storyline

• Yet another hype

• Define DevOps

• Expand DevOps

• Sell DevOps

• Kill DevOps!

Storyline

The six blind men and the hype

It’s DevOps

It’s DevOps

It’s DevOps

It’s DevOps It’s

DevOps It’s DevOps

• Yet another hype

• Define DevOps

• Expand DevOps

• Sell DevOps

• Kill DevOps!

Storyline

Patrick Debois

@patrickdebois

• 2008: “Agile Infrastructure”

• 2009: “DevOps” and

Devopsdays

www.jedi.be/blog/

The Godfather

John Willis @botchagalupe

2010: “CAMS” Culture,

Automation, Measurement, Sharing

http://itrevolution.com/devops-culture-part-1/

www.chef.io/blog/2010/07/16/what-devops-

means-to-me/

The Botchagalupe

A set of cultural norms,

technical practices,

and architectures*,

that enable organizations to have • fast flow of work from development through test and deployment

• while preserving world-class reliability, availability and security

Gene Kim, interviewed by Aprill Allen - http://knowledgebird.com/ interview-gene-kim-devops/* YouTube ITSM Global Podcast – Gene Kim

A relectant definition

Standardization dilemma

DevOps Institute

DASA

DevOps Handbook

The IT Skeptic

“Who owns

DevOps”

C

H

A

S

M

Architecture ~ the practically irreversible part of design

DevOps architecture

“But containers

seemed like such

a good idea

at the time…”

DevOps legacy 5 years from now

“Computing’s core challenge is

how not to make a mess of it”

Prof. E.W. Dijkstra, 1996

http://u-tx.net/people/dijkstra.html

Technical debt

1. Consider the performance

of the entire system

2. Create and amplify the

right-to-left feedback loops

3. Create a culture that fosters a) continual experimentation, taking risks, and learning

b) repetition and practice – the prerequisite to mastery

Three Ways of DevOps

Source: The Phoenix Project

Technical practices for:

1. Flow

2. Feedback

3. Continual experimentation and learning

4. Integrating information security, change

management, and compliance

Technical practices

Source: The DevOps Handbook

� Speed of change

� Operational behaviour (reliability, availability,

security)

? Cost

× Functionality

� Fun

DevOps = non-functional

IT performance

• Deployment frequency

• Lead time for changes

• Mean time to recover

• Change failure rate

Agile ‘versus’ DevOps

A DD A

A D A D

1 2

3 4

Specify

Acquire/Build

Configure

Integrate

Test

Deploy

Run

Support

DevOps versus Agile

IT Value Chain

DEV OPS USE

< - - - - - Agile - - - - - >

DevOps

REQ

Continuous…IntegrationTesting

DeliveryDeployment

Info

Req

App

Dev

App

Ops

Info

Use

PlatformDev

PlatformOps

InfraDev

InfraOps

DIY vs sourcing

Outsourcing Blog: http://allthingsitsm.com/devops-accelerating-it-evolution

• Yet another hype

• Define DevOps

• Expand DevOps

• Sell DevOps

• Kill DevOps!

Storyline

Dev

Ops

Architecture

QA

Supply

Security

Support

Business

Source: Dave van Herpen

The DevOps cast

12 Ways of DevOps

Dem Use

1

2

3

11

10

12

5 6 4 7 8 9

Systems thinking

Amplified

feedback loops

Culture of

continuous

experimentation

and learning

Dem

4

5

6 Use

7

8

9Dev Ops

“DevOps” on

http://allthingsitsm.com/

author/marksmalley/

Prequel Sequel

“The Business”

Van Haren Publishing

free e-book

BiSL Pocket Guide

http://bit.ly/BiSL-In-a-nutshell

• Yet another hype

• Define DevOps

• Expand DevOps

• Sell DevOps

• Kill DevOps!

Storyline

Sell me this DevOps

Profit

Revenue

Cost

Different

business

Better IT functionality

Quicker delivery of IT

Fewer/shorterIT outages

Cheaper/fewer

IT resources

Moreefficient IT

Lower

OPEX

More

sales

Higher

prices

Lower

CAPEX

Better

products

Better

relationships

More

efficient

Cheaper/fewer

resources

More

innovative

Your ITinitiative

More predictable performance

Lower

business riskSmaller

deviationsRisk

Sell me this DevOps

Profit

Revenue

Cost

Different

business

Better IT functionality

Quicker delivery of IT

Fewer/shorterIT outages

Cheaper/fewer

IT resources

Moreefficient IT

Lower

OPEX

More

sales

Higher

prices

Lower

CAPEX

Better

products

Better

relationships

More

efficient

Cheaper/fewer

resources

More

innovative

Your DevOpsinitiative

More predictable performance

Lower

business riskSmaller

deviationsRisk

• Yet another hype

• Define DevOps

• Expand DevOps

• Sell DevOps

• Kill DevOps!

Storyline

Dave van HerpenManagement Consultant

@daveherpen

Mark SmalleyThe IT Paradigmologist

@marksmalley 4 June 2014

Kill DevOps

www.flickr.com/photos/h-k-d

http://allthingsitsm.com/kill-devops/

Kill DevOps?

www.flickr.com/photos/h-k-d

KILL:

We’ve defined DevOps

We’ve expanded

DevOps

We know how to sell

DevOps

ITSMF UKPremier Gate, Easthampstead Road, Bracknell,

RG12 1JS, United Kingdom

Tel: +44 (0) 118 918 6500 | Web: www.itsmf.co.uk