4 Questions to Ask Your Dev Team

Slide 1

Slide 1 text

Slide 2

Slide 2 text

Why would I want to talk to developers? @HannahFoxwell @romrider42

Slide 3

Slide 3 text

Everything takes too long! Devs don’t care about production! @HannahFoxwell @romrider42

Slide 4

Slide 4 text

They don’t know what they need! I can do this cloud thing myself! @HannahFoxwell @romrider42

Slide 5

Slide 5 text

Who are we? Hannah Foxwell Jérôme Wiedemann Associate Director for Pivotal Labs Platform Services EMEA Associate Director for Pivotal Labs Platform Services EMEA We’re on a mission to build wildly successful Platform Teams. Technology is the easy part. People are the hard part! @HannahFoxwell @romrider42

Slide 6

Slide 6 text

Question 1: How are we going to work together? @HannahFoxwell @romrider42

Slide 7

Slide 7 text

Good fences make good neighbours. @HannahFoxwell @romrider42

Slide 8

Slide 8 text

IaaS Platform Application Platform Team Mission: “Build an amazing product and valuable service for my users!” Dev Ops Application Team Mission: “Build an amazing product and valuable service for my users!” Infrastructure Team Mission: “Build an amazing product and valuable service for my users!” @HannahFoxwell @romrider42

Slide 9

Slide 9 text

Some other patterns... Platform Eng AppDev WARNING: Only if you absolutely have to. Avoid silos with good communication and collaboration. Dev Ops AppOps Platform Ops Platform Application Dev Ops Tools Platform Application Dev Ops SRE Too much centralisation can become a constraint, but providing self serve tools can help developers focus on what’s important! SRE can be a separate team or it can be a set of practices adopted by everyone. @HannahFoxwell @romrider42

Slide 10

Slide 10 text

I Need More @HannahFoxwell @romrider42

Slide 11

Slide 11 text

The Platform is a Product Story 1 Story 3 Story 2 Story 1 Story 3 Story 2 Application Users Application Developers Platform Users Product Manager Platform Engineers Product Manager Think of application developers as your customers! @HannahFoxwell @romrider42

Slide 12

Slide 12 text

Question 2: What is your path to production? How can I help make it easier? @HannahFoxwell @romrider42

Slide 13

Slide 13 text

"Production is the happiest place on earth" Josh Long - @starbuxman @HannahFoxwell @romrider42

Slide 14

Slide 14 text

Production is where we deliver value to our users @HannahFoxwell @romrider42

Slide 15

Slide 15 text

So why are we so scared of production? @HannahFoxwell @romrider42

Slide 16

Slide 16 text

DORA's Aspect of Delivery Performance Source: https://cloud.google.com/devops/ @HannahFoxwell @romrider42

Slide 17

Slide 17 text

Automation helps you build reproducible workﬂows @HannahFoxwell @romrider42

Slide 18

Slide 18 text

Test Driven Development helps you build conﬁdence @HannahFoxwell @romrider42

Slide 19

Slide 19 text

Safely release code by including feature toggles @HannahFoxwell @romrider42

Slide 20

Slide 20 text

Question 3: What level of reliability do our users need? @HannahFoxwell @romrider42

Slide 21

Slide 21 text

Reliability is Fundamental @HannahFoxwell @romrider42

Slide 22

Slide 22 text

Reliability is Everyone’s Goal @HannahFoxwell @romrider42

Slide 23

Slide 23 text

Reliability is a Team Sport @HannahFoxwell @romrider42

Slide 24

Slide 24 text

Service Level Indicators (SLIs), Service Level Objectives (SLOs) and Error Budgets @HannahFoxwell @romrider42

Slide 25

Slide 25 text

Service Level Indicator (SLI) is a metric Service Level Objective (SLO) is a threshold @HannahFoxwell @romrider42

Slide 26

Slide 26 text

SLO Error Budget (per 28 Days) 99% 403 mins 99.5% 202 mins 99.9% 40.3 mins 99.95% 20.2 mins 99.99% 4.03 mins 99.999% 0.04 mins Your Error Budget is the inverse of your SLO @HannahFoxwell @romrider42

Slide 27

Slide 27 text

Who gets to use the Error Budget? @HannahFoxwell @romrider42

Slide 28

Slide 28 text

Sharing Responsibility for Users Happiness IaaS Platform Application SLO = 99.99% Error Budget = 4.03 minutes SLO = 99.95% Error Budget = 20.2 minutes SLO = 99.9% Error Budget = 40.3 minutes @HannahFoxwell @romrider42

Slide 29

Slide 29 text

Agree an Error Budget Policy before you need one @HannahFoxwell @romrider42

Slide 30

Slide 30 text

Example Error Budget Policy Service is performing at or above SLO Service has exceeded Error Budget in the preceding 4 week window A single incident consumes more than 20% of Error Budget over 4 weeks Continue to release changes as normal within agreed release policy Halt all changes and releases other than P1 and P2 issues or security ﬁxes Post-incident review. Must include at least 1 action to address the cause @HannahFoxwell @romrider42

Slide 31

Slide 31 text

Question 4: What are we going to do when things go wrong? @HannahFoxwell @romrider42

Slide 32

Slide 32 text

100% availability is NOT the right expectation @HannahFoxwell @romrider42

Slide 33

Slide 33 text

Only actionable alerts should trigger incident response @HannahFoxwell @romrider42

Slide 34

Slide 34 text

Replicate user interactions @HannahFoxwell @romrider42

Slide 35

Slide 35 text

Build conﬁdence with ﬁre drills @HannahFoxwell @romrider42

Slide 36

Slide 36 text

Blameless incident retrospective @HannahFoxwell @romrider42

Slide 37

Slide 37 text

So in summary... @HannahFoxwell @romrider42

Slide 38

Slide 38 text

Talk to each other @HannahFoxwell @romrider42

Slide 39

Slide 39 text

Ask these 4 simple questions: 1. How are we going to work together? 2. What is your path to production? 3. What level of reliability do our users need? 4. What are we going to do when things go wrong? Let’s work together! @HannahFoxwell @romrider42

Slide 40

Slide 40 text

Are we getting better at this? Ask these 4 simple questions: 1. How are we going to work together? 2. What is your path to production? 3. What level of reliability do our users need? 4. What are we going to do when things go wrong? @HannahFoxwell @romrider42