DevOps Theory vs. Practice: A Song of Ice and TireFire

A presentation at DevOpsDays Salt Lake City in May 2019 in Salt Lake City, UT, USA by Baruch Sadogursky

Slide 1

Slide 1

Software Engineering Theory vs. Practice: A Song of Ice and Tire Fire

Slide 2

Slide 2

Senior SRE Leader at Google Thought Leader, Disruptive Innovator Senior Software Engineer at Netflix SVP of Thoughts at Facebook Obviously better than you Disclaimer: absolutely

Slide 3

Slide 3

Official Hiptech Translator Native proficiency in Russian, Hebrew, English, Java, Go Curses in 18 more languages Fluent in Thought Leader gibberish Disclaimer: some of the above may or may not be true. @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 4

Slide 4

Baruch, Thought Leader Away! @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 5

Slide 5

Everybody’s software must be releasable at absolutely any time @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 6

Slide 6

Everyone must have 100% test automation @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 7

Slide 7

We do Continuous Security well. @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 8

Slide 8

Your greatest threat is an outage. Not an employee. @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 9

Slide 9

VMs are the enemy of DevOps. This is where you must focus your innovation. @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 10

Slide 10

You are a beautiful unique snowflake, as are your problems. No vendor could possibly understand them. @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 11

Slide 11

Our company is based in SF because that’s where the best engineers are. @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 12

Slide 12

THANK YOU! @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 13

Slide 13

Slide 14

Slide 14

How did we get here? @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 15

Slide 15

Slide 16

Slide 16

TIMEThereFOR BULLET POINTS could be text here too • Gotta love bullets • Gotta love bullets • Gotta love bullets • Gotta love bullets • Gotta love bullets • Gotta love bullets

Slide 17

Slide 17

Slide 18

Slide 18

TIMEThereFOR BULLET POINTS could be text here too • Gotta love bullets • Gotta love bullets • Gotta love bullets • Gotta love bullets • Gotta love bullets • Gotta love bullets

Slide 19

Slide 19

Slide 20

Slide 20

Cargo Cult @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 21

Slide 21

The Four Questions @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 22

Slide 22

The Four Questions 1. Is my organization/team ready to adopt a new tech? 2. Is it even a good tech? 3. What do I gain from adopting this tech? 4. Is this tech a good solution to my problem?

Slide 23

Slide 23

The Four Questions 1. Is my organization/team ready to adopt a new tech? 2. Is it even a good tech? 3. What do I gain from adopting this tech? 4. Is this tech a good solution to my problem?

Slide 24

Slide 24

Is my organization /team ready to adopt a new tech? 1. @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 25

Slide 25

• “A maturity model is a tool that Introducing maturity models helps people assess the current effectiveness of a person or group and supports figuring out what capabilities they need to acquire next in order to improve their performance. • In many circles maturity models have gained a bad reputation, but although they can easily be misused, in proper hands they can be helpful.” - • Martin Fowler @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 26

Slide 26

• “A maturity model is a tool that Introducing maturity models helps people assess the current effectiveness of a person or group and supports figuring out what capabilities they need to acquire next in order to improve their performance. • In many circles maturity models have gained a bad reputation, but although they can easily be misused, in proper hands they can be helpful.” - • Martin Fowler @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 27

Slide 27

Introducing maturity models Nicole Forsgren, Jezz Hamble, Gene Kim @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 28

Slide 28

Bad Maturity Models are Bad. Bad Maturity Models Good Maturity Models Goal Process Prescribed by the book One size doesn’t fit all Checkboxes for tools Focus on outcomes Write and forget Constantly evolve

Slide 29

Slide 29

Maturity model components Evaluation factors Scoring methodology Self assessment vs 3rd party assessment capability Progress tracking Visualization @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 30

Slide 30

Maturity Model Examples @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 31

Slide 31

Simple model @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 32

Slide 32

Progress planning Target Today @jbaruch @nashvilledevops In 2Q #DevOpsDays jfrog.com/shownotes

Slide 33

Slide 33

Leader board Team B Team A Team C Team D Team E @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 34

Slide 34

@jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 35

Slide 35

@jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 36

Slide 36

@jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 37

Slide 37

Account for different teams’ priorities @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 38

Slide 38

Model definition example System config as Code The infrastructure configuration is managed as code - e.g. no manual processes for configuring/setting up/ infrastructure. Differentiating: Infrastructure operates without any manual processes. All changes to the infrastructure or infrastructure capabilities are done through automation and policy only. Complete: Infrastructure operates without any manual processes. Some infrequent administrative activities may be initiated manually (although the activities themselves must be automated). Partial (Most): Infrastructure operates without any manual processes. Some infrequent administrative activities may be manual, pending automation. Partial (Much): Infrastructure operates with significant automation. Some processes still manual; pending automation. Partial (Some): Infrastructure requires significant care and feeding. Many processes still manual; pending automation. No Support: While some functions may be automated, they are generally kicked-off manually; and many functions are still fully manual. Large backlog of automation items. @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 39

Slide 39

Applying maturity models: DOs and DONT’s Only use primary colors Involve your teams in the model definition Let team self assess first and then assess together Partner with forward looking teams first Remember being at 100% is not a goal the model has to have a stretch goal Evolve the model from time to time And …. @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 40

Slide 40

Our message is: https://martinfowler.com/bliki/MaturityModel.html @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 41

Slide 41

@jbaruch Is it even a good tech? @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 42

Slide 42

@jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 43

Slide 43

@jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 44

Slide 44

@jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 45

Slide 45

@jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 46

Slide 46

Can I have my own? @jbaruch @nashvilledevops #DevOpsDays jfrog.com/shownotes

Slide 47

Slide 47

Slide 48

Slide 48

The Recap: The Four Questions 1. Is my organization/team ready to adopt a new tech? 2. Is it even a good tech? 3. What do I gain from adopting this tech? 4. Is this tech a good solution to my problem?