DevOps @ KnowIT - Speaker Deck

Slide 1

Slide 1 text

Hello!

Slide 2

Slide 2 text

* I’m Mårten * I tend to work at companies with blue logos

Slide 3

Slide 3 text

* Today, this: Omni * 13 devs (backend: 7+3 & frontend: 2+2) * I head up the backend & infrastructure team

Slide 4

Slide 4 text

Infrastructure aware development and vice versa

Slide 5

Slide 5 text

Why?

Slide 6

Slide 6 text

Awareness * Become aware of what happens outside “our bubble” * Become aware of why “things” are happening

Slide 7

Slide 7 text

Understanding * Understanding why things are the eay they are * Understanding that what appears bad to me, might appear good to someone else

Slide 8

Slide 8 text

Precision * Less confustion * Higher pace * Quicker to ﬁnd the “right direction”

Slide 9

Slide 9 text

Co-planning * If we understand and are aware it’ll be easier to plan together * If we plan together we’ll become aware and understand each other

Slide 10

Slide 10 text

We’re on the same team!

Slide 11

Slide 11 text

“No, we’re not!” * (get a grip)

Slide 12

Slide 12 text

co-lo get a sysops * in your team * (per team?) * contract or hire * full or part-time

Slide 13

Slide 13 text

managed hosting customer responsible technician * whom you assimilate! * get person on chat, mailing lists, etc * invite to lunch, AW, whatever

Slide 14

Slide 14 text

cloud == co-lo get a sysops * I consider cloud based servers as co-lo

Slide 15

Slide 15 text

PaaS sysop 2.0? * PaaS, e.g. Heroku, will force a bigger responsibility on DEV * and/or a completely different kind of OPS * I’m not sure here, yet

Slide 16

Slide 16 text

How?

Slide 17

Slide 17 text

Don’t know. * There’s no exact answer as to “how”

Slide 18

Slide 18 text

Why?

Slide 19

Slide 19 text

Higher pace. * Do X in half the time? * Do X with half the people involved? * More time and or people to do Y and Z!

Slide 20

Slide 20 text

Higher quality. * Avoid the most common mishaps? (without loosing pace!)

Slide 21

Slide 21 text

Higher awareness.

Slide 22

Slide 22 text

Higher engagement. * if more of the involved have higher awareness we’ll get a higher engagement and we’ll increase quality and deliver faster

Slide 23

Slide 23 text

Key. Words.

Slide 24

Slide 24 text

Cooperate. * Make it natural * Make it easy

Slide 25

Slide 25 text

Communicate. * Direct, clear, concise, transparent

Slide 26

Slide 26 text

The rest will “sort itself” out. * Not quite, but almost

Slide 27

Slide 27 text

Hints

Slide 28

Slide 28 text

Find “like-minded”

Slide 29

Slide 29 text

Invite. * Invite all “the others” to planning, stand-ups, coffee, AW, etc * As with all transformations it won’t happen in an instant and it’ll be shaped over time

Slide 30

Slide 30 text

Guerrilla cooperation. * (my personal favorite) * Tend to work really well * Easier to ask for forgiveness than approval

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

1. Get to know each other

Slide 33

Slide 33 text

1. Get to know each other 2. Involve each other

Slide 34

Slide 34 text

1. Get to know each other 2. Involve each other 3. Start doing things together

Slide 35

Slide 35 text

1. Get to know each other 2. Involve each other 3. Start doing things together 4. Think strategic together

Slide 36

Slide 36 text

1. Get to know each other 2. Involve each other 3. Start doing things together 4. Think strategic together 5. Stop viewing others as “others”

Slide 37

Slide 37 text

1. Get to know each other 2. Involve each other 3. Start doing things together 4. Think strategic together 5. Stop viewing others as “others” 6. Do a project together

Slide 38

Slide 38 text

Culture. * DevOps is culture * DevOps is not an automated infrastructure (automation is a product, project, whatevs) * DevOps is not a title * Culture happens when individuals work together

Slide 39

Slide 39 text

“An organizations culture isn’t in ‘the walls’. It’s in the people”