@jezhumble | #jenkinsworld | august 31, 2017
the devops transformation
Slide 2
Slide 2 text
@jezhumble
core principles and practices
the problem (why devops matters)
how does devops help?
how to get there
common obstacles
agenda
Slide 3
Slide 3 text
@jezhumble
“the enterprise”
Project A
Project B
Project C
DBAs
Infrastructure team
Service desk
Value stream
Operations
Engineering
Business
Ping!
Slide 4
Slide 4 text
@jezhumble
Project A
Project B
Project C
DBAs
Infrastructure team
Service desk
Value stream
Operations
Engineering
Business
Ping!
Project D
Let’s create
a new
product
enterprise projects
Slide 5
Slide 5 text
@jezhumble
Project A
Project B
DBAs
Infrastructure team
Service desk
Project D
We’re going
agile! Oh no!
Oh no!
Value stream
Operations
Engineering
Business
Slide 6
Slide 6 text
@jezhumble
Project A
Project B
DBAs
Infrastructure team
Service desk
Value stream
Operations
Engineering
Business
Project D
Our test-driven code
follows SOLID
principles
Shame it
doesn’t work
Change
management
Slide 7
Slide 7 text
how devops helps
Slide 8
Slide 8 text
@jezhumble
devops movement
a cross-functional community of practice dedicated to the study of
building, evolving and operating rapidly changing, secure, resilient
systems at scale
Slide 9
Slide 9 text
@jezhumble
what is continuous delivery?
The ability to get changes—features, configuration changes, bug
fixes, experiments—into production or into the hands of users
safely and quickly in a sustainable way.
Slide 10
Slide 10 text
@jezhumble
the iron triangle
Slide 11
Slide 11 text
Jon Jenkins, “Velocity Culture, The Unmet Challenge in Ops” | http://bit.ly/1vJo1Ya
Slide 12
Slide 12 text
@jezhumble
time to restore service
lead time for changes
release frequency
change fail rate
it performance
http://bit.ly/2014-devops-report
Slide 13
Slide 13 text
Jon Jenkins, “Velocity Culture, The Unmet Challenge in Ops” | http://bit.ly/1vJo1Ya
http://bit.ly/2016-devops-report
Slide 14
Slide 14 text
@jezhumble
the alignment trap
“Avoiding the Alignment Trap in IT,“ David Shpilberg, Steve Berez, Rudy Puryear and Sachin Shah
MIT Sloan Management Review Magazine, Fall 2007.
Slide 15
Slide 15 text
@jezhumble
how quickly can I get a critical fix to users?
how quickly can i get feedback?
how quickly can I restore service?
how quickly can I validate if a feature is valuable?
why lead time is important
Slide 16
Slide 16 text
@jezhumble
“Evaluating well-designed and executed experiments that
were designed to improve a key metric, only about 1/3 were
successful at improving the key metric!”
do less
Kohavi et al, “Online Experimentation at Microsoft” | http://stanford.io/130uW6X
Slide 17
Slide 17 text
core devops principles and practices
Slide 18
Slide 18 text
scrum-
fall
water-
Slide 19
Slide 19 text
@jezhumble
build quality in
“Cease dependence on mass
inspection to achieve quality.
Improve the process and
build quality into the product in
the first place”
W. Edwards Deming
Slide 20
Slide 20 text
Mainline Server
Develop
Build
Build
pull
Local
Workstation
Build
push
✔
Done!
Slide 21
Slide 21 text
Mainline Server
Develop
Build
Build
pull
Local
Workstation
Build
push
✔
Done!
Everyone Commits
To the Mainline
Every Day
Slide 22
Slide 22 text
@jezhumble
continuous integration at scale
Jason Leyba | http://queue.acm.org/blogposting.cfm?id=78323
Slide 23
Slide 23 text
John Penix | “Large Scale Continuous Testing in the Cloud” | http://bit.ly/1BYMf70
Slide 24
Slide 24 text
@jezhumble
deployment pipeline
Slide 25
Slide 25 text
@jezhumble
different types of testing
Functional acceptance
tests
Showcases
Usability testing
Exploratory testing
Unit tests
Integration tests
System tests
Non-functional
acceptance tests
(performance, scaling, ...)
Business facing
Technology facing
Critique project
Support programming
AUTOMATED
AUTOMATED
MANUAL
MANUAL / AUTOMATED
Slide 26
Slide 26 text
@jezhumble
infrastructure-as-code
Slide 27
Slide 27 text
common obstacles
Slide 28
Slide 28 text
it’s about culture and architecture
not
process, tools, organizational structure
Slide 29
Slide 29 text
@jezhumble
high trust culture
Westrum, “A Typology of Organizational Cultures” | http://bmj.co/1BRGh5q
how organizations process information
Slide 30
Slide 30 text
@jezhumble
internet architecture
Success on the web depends on
“the ability to consistently create
and deploy reliable software to an
unreliable platform that scales
horizontally”
Jesse Robbins, “Master of Disaster” @ Amazon| @jesserobbins | http://oreil.ly/1HRKUVE
You build it,
You run it
werner vogels, cto, amazon | http://bit.ly/11UJjmN
Slide 36
Slide 36 text
Project A
Project B
Project C
DBAs
Infrastructure team
Service desk
Value stream
Operations
Engineering
Business
Treat these services
as if they were products
Slide 37
Slide 37 text
@jezhumble
think product
Service desk
Value stream
Operations
Products / Services
Ping!
PaaS
Ops management
Slide 38
Slide 38 text
@jezhumble
talk to other teams
agree and communicate measurable business goals
give teams support and resources to experiment
keep going
achieve quick wins and share learnings
the journey
“6 Steps To Survive A DevOps Transformation” | http://ubm.io/1dKJajR