The Journey of a DevOp - Speaker Deck

Slide 1

Slide 1 text

The Journey of a DevOp

Slide 2

Slide 2 text

What is a DevOp?

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

What kind of Journey?

Slide 5

Slide 5 text

Or if you prefer … https://www.youtube.com/watch?v=b4ztfrr8ﬂs

Slide 6

Slide 6 text

Who Am I? • Software Engineer • In my 8th year of experience

Slide 7

Slide 7 text

The ideas contained in this presentation are not unique. ! DevOps is not unique.

Slide 8

Slide 8 text

What is DevOps?

Slide 9

Slide 9 text

A culture of collaboration centered on nurturing business goals quickly while developing a humane work environment.

Slide 10

Slide 10 text

10 Deploys Per Day Dev & ops cooperation at Flickr ! John Allspaw & Paul Hammond Velocity 2009

Slide 11

Slide 11 text

Why DevOps? http://www.infocaptor.com/dashboard/venture-capital- investment-analytics-on-20-years-of-investment-data

Slide 12

Slide 12 text

Is DevOps About Tools? ! NO

Slide 13

Slide 13 text

But Tools Matter

Slide 14

Slide 14 text

Tools enable automation. Automation means you can work on something more valuable to the company.

Slide 15

Slide 15 text

Experiment. Find the right tool. Use open source to try.

Slide 16

Slide 16 text

Does DevOps mean Dev and Ops become one and the same? ! No.

Slide 17

Slide 17 text

You’ll be a better developer if you know some about operations, and you’ll be better at operations if you know something about development.

Slide 18

Slide 18 text

And Dev and Ops will both be better if they know something about the business.

Slide 19

Slide 19 text

Should developers be on call? ! Maybe.

Slide 20

Slide 20 text

Should you have a DevOps team? ! Maybe.

Slide 21

Slide 21 text

Let’s talk process

Slide 22

Slide 22 text

Process replaces communication, because communication doesn’t scale

Slide 23

Slide 23 text

– Paraphrase of Rands (Michael Lopp) randsinrespose.com Process always starts with a reason. Determine the reason for it and change it if the reason no longer holds.

Slide 24

Slide 24 text

You get the behavior you optimize for.

Slide 25

Slide 25 text

You get the behavior you reward for.

Slide 26

Slide 26 text

So you still want to try this DevOps thing?

Slide 27

Slide 27 text

Management buy-in helps.

Slide 28

Slide 28 text

So how do I get management buy-in?

Slide 29

Slide 29 text

Model the behavior you want

Slide 30

Slide 30 text

Idea from Making Things Happen, by Scott Berkun (Chpt. 16 Power and Politics) Use your sphere of inﬂuence.

Slide 31

Slide 31 text

This all takes time, because changing culture takes time.

Slide 32

Slide 32 text

DevOps is hard because it makes everyone vulnerable.

Slide 33

Slide 33 text

Because trust makes you vulnerable, and DevOps is fundamentally about trust.

Slide 34

Slide 34 text

People fear vulnerability. They fear trust. They resist change.

Slide 35

Slide 35 text

- Courtney Nash http://radar.oreilly.com/2015/01/chop-wood-carry-water.html Chop wood, carry water.

Slide 36

Slide 36 text

– John Allspaw, On Being a Senior Engineer http://www.kitchensoap.com/2012/10/25/on-being-a-senior- engineer/ Have generosity of spirit.