DevOps: how the Industrial Revolution got us here

Jonathan Fletcher

Enterprise Architect, Technology and Platform Lead

v1.1

Me

• Jonathan Fletcher

• Architect in Hiscox Group IT since 2012

• Ex Dev

• Ex Ops

• http://enterprisedevops.blogspot.com

• http://www.devops.com

• @FletcherJofanon

2

The 1700’s

3

4

The industrial revolution

• Occurred in England some time in the mid-1700’s

• Largely in response to textile competition arising from India

Boring…so what?

• Led us from hand manufacturing techniques to machines

• Led to new processes including increased specialisation of roles and new ways of scaling production

5

The Spinning Jenny

6

Luddites

7

Getting there...

8

Now

9

IT today

10

I’m a business analyst

I’m a DBA

I’m a developer

I work in support

I’m an infrastructure

engineer

I’m a business stakeholder

I’m a release manager

I’m a security consultant

Common complaints

• “Throw it over the wall” behaviour - it’s not my problem

• Lack of holistic understanding of the software delivery lifecycle

• Slow pace of change

• Expensive cost of change

• Late discovery of issues in the project lifecycle

• Unaligned goals and incentives – pulling in different directions

11

Alignment of goals

More process review

s M

ore change control reviews

More deploym

ent freezes M

ore standards control boards

Mor

e fr

eque

nt c

hang

esLo

wer

tole

ranc

e fo

r ou

tage

Mor

e co

mpl

ex a

pplic

atio

nsM

ore

com

plex

dep

loym

ents

Do more! Do less!

RFC’sCABDeployment guideRollback guideDaily status callsStaff availabilityIssue trackingEnvironment bookingEscalation processesEmergency processesSmall change processesetc etc

Mr. Dev Mr. Ops

Is DevOps the right name?

• Why do we think the issue of working well together and aligning goals is limited to Development and Operations?

• Shouldn’t everyone involved in the change process should work together to accomplish shared goals?

• DevTestBizThingyOps DevTestBizThingySecOps should be the real name © J.Fletcher

DevOps – so what is it?

14

• “Bad behaviour arises when you abstract people away from the consequences of their actions” – Jez Humble

• DevOps is a culture of empathy, shared goals and incentives

This says everything

15

Shared goals, incentives, empathy & transparency

16

17

Automation benefits

• 150 deployments in the last 3 days in one application alone

• The week before go-live on our biggest ever change program we reduced 17.5 man days of effort to about 10 minutes

• Help enable changing a 10 week change cycle down to 2 weeks

• We went from 1 person knowing how to do to do a release to thousands (kind of!)

DevOps has visibility at the highest levels

18

Project Sponsor

MyBoss

DevOps – how?

19

1. Employ the right people in the right team structure (and yes that includes you security chaps!)

2. Empower the team – let them make the right decisions

3. There are processes and tools that help align working practises to achieve empathy and shared goals (such as increasing the pace of change)

4. Commonly large amounts of automation is prevalent in a DevOps environment to create metrics, reduce manual wasted effort and increase the pace of change

Remember those naughty Luddites!

20

Questions?

21