devopsdays downunder-vfinal

DEVOPSwhat’s in a word

Patrick Debois - Devopsdays DownUnder 2011Friday 22 July 2011

DEVOPSis everywhere

Friday 22 July 2011

DEVOPS

Friday 22 July 2011

DEV OPS

Friday 22 July 2011

HISTORICAL DRIVER #1

Agile (Development)

BUSINESS TESTDEVProject Mgr

OPS

Friday 22 July 2011

HISTORICAL DRIVER #1

Agile (Development)

BUSINESS TESTDEVProject Mgr

PR

ES

SU

RE

OPS

Friday 22 July 2011

HISTORICAL DRIVER #1

Agile (Development)

BUSINESS TESTDEVProject Mgr

PR

ES

SU

RE

OPS

Friday 22 July 2011

HISTORICAL DRIVER #1

Agile (Development)

BUSINESS TESTDEVProject Mgr

PR

ES

SU

RE

OPS

Friday 22 July 2011

HISTORICAL DRIVER #1

Agile (Development)

BUSINESS TESTDEVProject Mgr

PR

ES

SU

RE

PRESSURE ON OPS

OPS

Friday 22 July 2011

HISTORICAL DRIVER #2

BUSINESS OPSTESTDEVProject Mgr

Virtualization/CloudLarge Scale (Web)ops

Friday 22 July 2011

HISTORICAL DRIVER #2

BUSINESS OPSTESTDEVProject Mgr

PR

ES

SU

RE

Virtualization/CloudLarge Scale (Web)ops

Friday 22 July 2011

3 Layers of DEVOPS

OPSDEV

People

Process

Tools

Friday 22 July 2011

OPSDEV

People

Process

Tools

Tool enablers: Automation and TestingFriday 22 July 2011

OPSDEV

People

Process

Tools Continuous Delivery

Tool enablers: Automation and TestingFriday 22 July 2011

OPSDEV

People

Process

Tools Continuous Delivery Infrastructure as Code

Tool enablers: Automation and TestingFriday 22 July 2011

OPSDEV

People

Process

Tools Continuous Delivery Infrastructure as Code

Tool enablers: Automation and TestingFriday 22 July 2011

OPSDEV

People

Process

Tools Continuous Delivery Infrastructure as Code

Tool enablers: Automation and TestingFriday 22 July 2011

OPSDEV

People

Process

Tools Continuous Delivery Infrastructure as Code

People Enablers: Multi Disciplinary CollaborationFriday 22 July 2011

OPSDEV

People

Process

Tools Continuous Delivery Infrastructure as Code

People Enablers: Multi Disciplinary Collaboration

Developers

Friday 22 July 2011

OPSDEV

People

Process

Tools Continuous Delivery Infrastructure as Code

People Enablers: Multi Disciplinary Collaboration

Developers Sysadmins

Friday 22 July 2011

OPSDEV

People

Process

Tools Continuous Delivery Infrastructure as Code

People Enablers: Multi Disciplinary Collaboration

Developers Sysadmins

Testers

Friday 22 July 2011

OPSDEV

People

Process

Tools Continuous Delivery Infrastructure as Code

People Enablers: Multi Disciplinary Collaboration

Developers Sysadmins

Testers

Friday 22 July 2011

OPSDEV

Small and frequent successful iterationsFriday 22 July 2011

OPSDEV

Small and frequent successful iterationsFriday 22 July 2011

OPSDEV

Small and frequent successful iterationsFriday 22 July 2011

Creates a feedback loop

OPSDEV

Friday 22 July 2011

OPSDEV

Friday 22 July 2011

OPSDEVBeing Professional

Friday 22 July 2011

OPSDEVBeing Professional

Fosters Collaboration

Friday 22 July 2011

OPSDEV

Increases TrustBeing Professional

Fosters Collaboration

Friday 22 July 2011

OPSDEV

Increases TrustBeing Professional

Generates RespectFosters Collaboration

Friday 22 July 2011

OPSDEV

Increases TrustBeing Professional

Generates RespectFosters Collaboration

Stop being an asshole

Friday 22 July 2011

OPSDEV

creating a cross-silo positive feedback loopFriday 22 July 2011

As part of the bigger feedback loop

BUSINESS MARKETOPSDEV

Friday 22 July 2011

As part of the bigger feedback loop

BUSINESS MARKETOPSDEV

Time to Market

Friday 22 July 2011

As part of the bigger feedback loop

BUSINESS MARKETOPSDEV

Faster Feedback

Time to Market

Friday 22 July 2011

As part of the bigger feedback loop

BUSINESS MARKETOPSDEV

Faster Feedback

Time to Market

Frictionless IT

Friday 22 July 2011

#1 DEVOPS Questionhow do I get started?

Friday 22 July 2011

It’s no different from introducing any other change

Friday 22 July 2011

Be ready to face the critics

Tip 1

there will be resistance

Friday 22 July 2011

OPSDEVis a SCAM

http://teddziuba.com/2011/03/devops-scam.htmlFriday 22 July 2011

OPSDEVis nothing new

LeanKanbanAgile

TocReliable EngineeringAutomation

TestingScrumConfig MgmtSystems Thinking

Critic 1

Friday 22 July 2011

OPSDEVtrue, difference is, devops actively seeks

cross-silo collaboration by applying existing concepts

LeanKanbanAgile

TocReliable EngineeringAutomation

TestingScrumConfig MgmtSystems Thinking

Critic 1

Friday 22 July 2011

OPSDEVwe’ve been doing #devops before there was a term

Critic 2

Friday 22 July 2011

OPSDEVgood for you!

now that we have term we can tag/share stories.

Why don’t you share yours?

Critic 2

Friday 22 July 2011

OPSDEVis a bad name

Critic 3

Friday 22 July 2011

akabussdevtestqanetsecsysnetops

OPSDEVis a bad name

Critic 3

Friday 22 July 2011

aka*-ops

OPSDEVis a bad name

Critic 3

Friday 22 July 2011

OPSDEVsomehow the term stuck,

it’s not important.

#devops is inclusive,Think *dev*ops*

Critic 3

Friday 22 July 2011

OPSDEVis too ops centric

Critic 4

is too dev centricis too ...... centric

Friday 22 July 2011

OPSDEVpeople have different backgrounds.

Therefore their collaboration focus will vary

Critic 4

Friday 22 July 2011

OPSDEVis too broad

there are 20+ definitions

Critic 5

Friday 22 July 2011

OPSDEVSimilar to cloud,

but does that make it any less useful?

Collaboration can take many forms. Only by doing it you realize full potential

Critic 5

Friday 22 July 2011

OPSDEVis too tools centric

not enough business focused

Critic 6

Friday 22 July 2011

OPSDEVit’s NOT NOT NOT NOT NOT NOT

NOT NOT NOT about the toolsbut tools can help collaboration

it’s the way you use the tools

Critic 6

PackagingDeployment

LoggingConfig Mgt

Monitoringif used for cross-silo feedback?

devopsyes

no

opsFriday 22 July 2011

OPSDEVis only for

startups & small businesses

Critic 7

Friday 22 July 2011

OPSDEVcollaboration is easier

in startups but ... large orgs need it more

Critic 7

Friday 22 July 2011

OPSDEV

is not gonna workaround here

Critic 8

Friday 22 July 2011

OPSDEVpeople said the same thing about

collaboration ideas likefacebook, wikipedia, wiki

a horizontal mindset breaks barriers

Critic 8

Friday 22 July 2011

OPSDEVwill decrease security

Critic 9

all devs have root accessaka

aka

you can’t audit a continuous deployment

Friday 22 July 2011

OPSDEVrepeatable process improves audit-able

Critic 9

faster feedback prevents failure in production

shared responsibility != no responsibility

it’s about continuous (value) delivery not deployment

multiple eyes principle appliesFriday 22 July 2011

OPSDEVwill render OPS obsolete

Critic 10

Friday 22 July 2011

OPSDEVcloud/saas abstraction

changes the context

Critic 10

monitor, backup, failover, ...will occur at a different level

every abstraction is ‘leaky’

Friday 22 July 2011

OPSDEVthe separation is blurring

Critic 10

collaborating specialists

context changes roles

Friday 22 July 2011

OPSDEVautomation frees time

Critic 10

to spend on design and on things that matter

Friday 22 July 2011

OPSDEVrequires ‘elite’ people

Critic 11

Friday 22 July 2011

OPSDEVeverybody can collaborate

Critic 11

cross-training helpsnot asshole-proof though

Friday 22 July 2011

OPSDEV

is a buzz word and will die soon

nothing more than cumbaya

Critic 12

has jumped the shark

has been taken over by the vendorsFriday 22 July 2011

OPSDEVsurveys shows increase in collaboration

Critic 12

is currently a differentiator and will become a given

tools vendors - only fools belief tools can solve their ‘human’ level problems

Friday 22 July 2011

don’t spend too much time with the nay-sayers.

focus on finding allies

Tip 2

Friday 22 July 2011

seek management support

if not , impact will be limited

Tip 3

Friday 22 July 2011

pick a small project and make it work.

Success builds trust better than anything else

Tip 4

Friday 22 July 2011

pick a problem area where there is real pain.

This increases willingness for change

Tip 5

Friday 22 July 2011

show don’t tell

Tip 6

Friday 22 July 2011

be bold go beyond your traditional silo

is someone really stopping you ?

Tip 7

Friday 22 July 2011

celebrate successgive credit to people

communicate results

Tip 8

Friday 22 July 2011

measure improvements

Tip 9

Friday 22 July 2011

retrospective

inspect and adapt

Tip 10

Friday 22 July 2011

OPSDEV

if you have a devops team,you’re doing it wrong

should we have a separate devops team?

Question 1

devops is not a jobtitleFriday 22 July 2011

OPSDEVan initial change team/taskforce

makes sense (temporary)

Question 1

the term is currently a good SEO term for hiring

open minded peopleFriday 22 July 2011

OPSDEV

how to measure success?

Question 2

Friday 22 July 2011

OPSDEVyou can’t directly

measure collaboration.(black-hole theory)

measure it through other results.Increase in quality/performance/...

Question 2

Friday 22 July 2011

OPSDEV

where is the manifesto?

Question 3

Friday 22 July 2011

OPSDEVre-read the agile manifestowith a more open mindset

Question 3

a specific devops manifesto is kind of counter-intuitive

Friday 22 July 2011

OPSDEVhow do you make it work with ITIL?

Question 4

does it replace ITIL?Friday 22 July 2011

OPSDEVnothing in ITIL excludes collaboration

Question 4

most implementations became bureaucratic and avoid change.

That should be uncontrolled changeFriday 22 July 2011

OPSDEV

Idea of an ‘reverse engineered/manual’ CMDB is changing

Question 4

Friday 22 July 2011

OPSDEV

Question 4

automation drives “standard changes”tests create “objective” acceptance

CAB becomes new bottleneckvs ‘Let the team decide’

Friday 22 July 2011

OPSDEVis there a

‘Windows’ devops?

Question 5

Friday 22 July 2011

OPSDEVit’s not about the tools.

At the tools level, Windows world has a more GUI , closed source history

people are working on it.

Question 5

Friday 22 July 2011

OPSDEVis there a devops

certification?

Question 6

Friday 22 July 2011

OPSDEVreally?

last thing we need isa process police

Question 6

Friday 22 July 2011

OPSDEV

so where is the #!?#! cookbook?

Question 7

Friday 22 July 2011

OPSDEV

guiding principles

Agile Lean Kanban engineering practices

Question 7

Friday 22 July 2011

OPSDEV

it’s rather new.give us a break,

we’re still collecting data

Question 7

Friday 22 July 2011

OPSDEV

most stories are on technical/tools level

infrastructure as code continuous deliverytesting

Question 7

Friday 22 July 2011

OPSDEV

need more stories on the process level

Question 7

Friday 22 July 2011

OPSDEVpair admin + developerdevelopers wear pagers

rotate roles/responsibilitiesuse of kanban in ops

devops and ITILpost-mortem as feedback

...

Question 7

Friday 22 July 2011

OPSDEVit’s a grass roots

movement.This is your chance!

Question 7

Friday 22 July 2011

OPSDEVhelp us with your stories

Question 7

Friday 22 July 2011

OPSDEVthat’s what devopsdays

is about

Friday 22 July 2011

OPSDEV

Thank you for being here!

Friday 22 July 2011

OPSDEVThank you for being

awesome!

Friday 22 July 2011

OPSDEVis a verb !

Enabling, Participating, Improving the feedback loop

Friday 22 July 2011