DevOps: the Data
and the Myths
Michael Stahnke
Director of Engineering
@stahnma
Slide 2
Slide 2 text
No content
Slide 3
Slide 3 text
No content
Slide 4
Slide 4 text
No content
Slide 5
Slide 5 text
Demographics
Slide 6
Slide 6 text
No content
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
Employees in high-performing
organizations are 2.2 times
more likely to recommend
their organization as a great
place to work.
Slide 9
Slide 9 text
No content
Slide 10
Slide 10 text
No content
Slide 11
Slide 11 text
No content
Slide 12
Slide 12 text
MTTR
Slide 13
Slide 13 text
Change failure rate
Slide 14
Slide 14 text
Isaac Newton’s laws of
devops
Slide 15
Slide 15 text
No content
Slide 16
Slide 16 text
Devops is…
Slide 17
Slide 17 text
Working together
Slide 18
Slide 18 text
Shared Pain
Slide 19
Slide 19 text
No content
Slide 20
Slide 20 text
No content
Slide 21
Slide 21 text
No content
Slide 22
Slide 22 text
No content
Slide 23
Slide 23 text
Cultural movement
Slide 24
Slide 24 text
“It is impossible to exceed expectations.”
Slide 25
Slide 25 text
No content
Slide 26
Slide 26 text
No content
Slide 27
Slide 27 text
No content
Slide 28
Slide 28 text
No content
Slide 29
Slide 29 text
Stability vs velocity
Slide 30
Slide 30 text
No content
Slide 31
Slide 31 text
No content
Slide 32
Slide 32 text
No content
Slide 33
Slide 33 text
No content
Slide 34
Slide 34 text
People, process, tools,
measurement
Slide 35
Slide 35 text
People
Slide 36
Slide 36 text
People don’t buy what you do, they
buy why you do it.
Simon Sinek
http://bit.ly/sinektedtalk
Slide 37
Slide 37 text
care about the
business, why?
Slide 38
Slide 38 text
Diversity
Slide 39
Slide 39 text
Align incentives.
Slide 40
Slide 40 text
Pattern 1:
Smooth operations
● Devs can teach ops about agile
development practices and ops can help
devs understand how their apps will run
in production.
● This pattern works really well for smaller
organizations, but it’s extremely
important in this structure to have a
common toolchain between dev and ops
to facilitate better collaboration.
Dev Ops
Slide 41
Slide 41 text
Pattern 2:
Cross-functional team
● Consists of devs, testers, ops, product owner, etc.
● Focused on delivering a single application
● Self-sufficient
● Optimized for throughput
Slide 42
Slide 42 text
Pattern 3:
DevOps team
● Consists ideally of devs with systems
experience, or sysadmins with programming
experience
● Focused on automating pain points
● Responsible for building a platform that
allows devs to self-service
● Provides a toolchain to enable devs to build,
test and deploy their systems
● Coaches other teams
Dev Ops
DevOps
Slide 43
Slide 43 text
No content
Slide 44
Slide 44 text
continuous
improvement
Slide 45
Slide 45 text
continuous learning
Slide 46
Slide 46 text
collaboration
Slide 47
Slide 47 text
No content
Slide 48
Slide 48 text
Process
Slide 49
Slide 49 text
No content
Slide 50
Slide 50 text
No content
Slide 51
Slide 51 text
No content
Slide 52
Slide 52 text
No content
Slide 53
Slide 53 text
No content
Slide 54
Slide 54 text
Value stream map
Slide 55
Slide 55 text
No content
Slide 56
Slide 56 text
Just enough process
Slide 57
Slide 57 text
collaboration to build
process
Slide 58
Slide 58 text
Optimized for cycle
time - iteration
Slide 59
Slide 59 text
Quality
Slide 60
Slide 60 text
Security
Slide 61
Slide 61 text
No content
Slide 62
Slide 62 text
No content
Slide 63
Slide 63 text
ITIL
Slide 64
Slide 64 text
No content
Slide 65
Slide 65 text
No content
Slide 66
Slide 66 text
No content
Slide 67
Slide 67 text
No content
Slide 68
Slide 68 text
Tools
Slide 69
Slide 69 text
DevOps toolchain
69
Version control
Configuration
management
Continuous Integration
Deployment
tools
Monitoring
and
others
…
and
others
…
Slide 70
Slide 70 text
DevOps toolchain
70
Version control
Configuration
management
Continuous Integration
Deployment
tools
Monitoring
and
others
…
and
others
…
Slide 71
Slide 71 text
Version Control
Slide 72
Slide 72 text
Configuration
Management
Slide 73
Slide 73 text
Continuous Integration
Slide 74
Slide 74 text
Deployment
Slide 75
Slide 75 text
Monitoring
Slide 76
Slide 76 text
Measurements
Slide 77
Slide 77 text
No content
Slide 78
Slide 78 text
No content
Slide 79
Slide 79 text
Why
Slide 80
Slide 80 text
No content
Slide 81
Slide 81 text
No content
Slide 82
Slide 82 text
No content
Slide 83
Slide 83 text
No content
Slide 84
Slide 84 text
No content
Slide 85
Slide 85 text
Metrics gamed
Slide 86
Slide 86 text
No content
Slide 87
Slide 87 text
No content
Slide 88
Slide 88 text
No content
Slide 89
Slide 89 text
Failure: 32K per year -
4.5 m/year
Slide 90
Slide 90 text
No content
Slide 91
Slide 91 text
Quote 1
Slide 92
Slide 92 text
The shortest path to better software
Myth #1:
92
There’s no direct customer/business value for adopting DevOps Practices
Slide 93
Slide 93 text
The shortest path to better software
Myth #2:
93
There’s no significant return on investment in applying DevOps principles
to legacy applications
Slide 94
Slide 94 text
The shortest path to better software
Myth #3:
94
DevOps only works with ‘unicorn’ companies and not traditional enterprise
businesses like ours
Slide 95
Slide 95 text
The shortest path to better software
Myth #4:
95
Improvement via DevOps principles requires spare time and people that we simply don’t have
Slide 96
Slide 96 text
The shortest path to better software
Myth #5:
96
We have regulatory and compliance requirements that preclude the adoption of
DevOps principles
Slide 97
Slide 97 text
The shortest path to better software
Myth #6:
97
We don’t have any problems that adopting DevOps principles and practices would fix
Be “good at getting better”
Move faster
Eliminate the most frustrating parts of work
Slide 98
Slide 98 text
Learning is not
compulsory, but neither is
survival.
Edward W. Deming
http://bit.ly/deming14pts
Slide 99
Slide 99 text
No content
Slide 100
Slide 100 text
• Drive from culture and org
• Optimize for feedback, and cycle time
• Tools model your process
• Measure what matters
• Iterate (small batch changes
Slide 101
Slide 101 text
Get your copy of the
2016 State of DevOps Report
puppet.com/devops-report-2016