WHO OWNS CHAOS? - Speaker Deck

Slide 1

Slide 1 text

PRESENTED BY Who is responsible for chaos? Chaos Conf Joyce Lin Lead Developer Advocate, Postman @petuniaGray @postmanClient

Slide 2

Slide 2 text

Joyce Lin Lead Developer Advocate, Postman Postman is an API Development Environment (ADE) used by more than 8 million people. For many teams, Postman is an everyday tool that helps people work with APIs more eﬃciently. @petuniaGray

Slide 3

Slide 3 text

TITL E 250 million + APIs 400,000 + companies 8 million + developers @petuniaGray

Slide 4

Slide 4 text

Who is responsible for chaos? @petuniaGray

Slide 5

Slide 5 text

Known Chaos Engineering tools and engineers @petuniaGray

Slide 6

Slide 6 text

Which job titles are doing chaos? @petuniaGray

Slide 7

Slide 7 text

@petuniaGray By Job Title

Slide 8

Slide 8 text

It boils down to who gets paged - if that’s an SRE or Ops team they have the most incentive to start doing this work and making their lives better. - Kolton Andrus, CEO at Gremlin @petuniaGray

Slide 9

Slide 9 text

Responsibilities •  Chaos specialists @petuniaGray

Slide 10

Slide 10 text

Responsibilities •  Chaos specialists •  Deployment and uptime @petuniaGray

Slide 11

Slide 11 text

Responsibilities •  Chaos specialists •  Deployment and uptime •  Incident management @petuniaGray

Slide 12

Slide 12 text

Responsibilities •  Chaos specialists •  Deployment and uptime •  Incident management •  Domain knowledge experts @petuniaGray

Slide 13

Slide 13 text

Responsibilities •  Chaos specialists •  Deployment and uptime •  Incident management •  Domain knowledge experts •  * Testing in Production @petuniaGray

Slide 14

Slide 14 text

Roles •  Site Reliability engineers •  Production engineers •  DevOps engineers •  InfoSec engineer •  Research analyst @petuniaGray

Slide 15

Slide 15 text

Why aren’t testers doing chaos? @petuniaGray

Slide 16

Slide 16 text

Before there was Chaos Engineering, there was Chaos Testing @petuniaGray

Slide 17

Slide 17 text

@petuniaGray Software Development Lifecycle Planning Design Development Testing Maintenance

Slide 18

Slide 18 text

@petuniaGray It was called chaos testing

Slide 19

Slide 19 text

@petuniaGray Software Development Lifecycle Planning Design Development Testing Maintenance

Slide 20

Slide 20 text

The biggest limitation in the fear of delivering software faster is the focus on adding more pre-release testing. - Abby Bangser, Platform Test Engineer at MOO @petuniaGray

Slide 21

Slide 21 text

...building confidence that we aren’t fragile. - Abby Bangser, Platform Test Engineer at MOO @petuniaGray

Slide 22

Slide 22 text

Testers doing chaos? •  Focused on pre-release testing •  Early stages of chaos automation @petuniaGray

Slide 23

Slide 23 text

Who can start a chaos program? @petuniaGray

Slide 24

Slide 24 text

Who has? •  Insights @petuniaGray

Slide 25

Slide 25 text

Who has? •  Insights •  Access @petuniaGray

Slide 26

Slide 26 text

Who has? •  Insights •  Access •  Buy-in @petuniaGray

Slide 27

Slide 27 text

Perhaps aggregate bits and pieces from different [resilience engineering] frameworks that appeal to you, and then create a practice around it. - Casey Rosenthal, CEO at Verica @petuniaGray

Slide 28

Slide 28 text

I wish the best of luck to you in that undertaking, but I wouldn’t wager that you get it right on your first try. Or your second. - Casey Rosenthal, CEO at Verica @petuniaGray

Slide 29

Slide 29 text

Infrastructure Talent Goals Maturity Industry So who owns chaos? @petuniaGray

Slide 30

Slide 30 text

Final lightning thoughts @petuniaGray

Slide 31

Slide 31 text

More adoption of chaos engineering @petuniaGray

Slide 32

Slide 32 text

A shift in roles and responsibilities @petuniaGray

Slide 33

Slide 33 text

Building a culture of resilience @petuniaGray

Slide 34

Slide 34 text

@petuniaGray Thank you!

Slide 35

Slide 35 text

Resources ●  Building resilient APIs with chaos engineering - Joyce Lin ●  Chaos people and tools - Chaos Engineering Slack Community ●  Introducing Chaos Engineering - Netflix blog 2014 @petuniaGray