[webinar] the changing role of release engineering in a devops world with j. paul reed
TRANSCRIPT
The Changing Role of Release Engineering in
a DevOps WorldJ. Paul Reed
Managing PartnerRelease Engineering Approaches
2
@jpaulreed
A Little Survey
3
@jpaulreed
Back in the Day
HumbleBeginningsas aBuild/Release Monkey…
4
@jpaulreed
Back in the Day
5
@jpaulreed
J. Paul Reed @jpaulreed on Managing Partner at Release
Engineering Approaches The Ship Show alumnus 15+ years build/release
engineering experience Today: A “DevOps™ Consultant”
6
@jpaulreed
Shippin’ Bits
7
@jpaulreed
“Yeeahhh... so what would you... say ya do here?”
8
@jpaulreed
The Elephant in the Room
9
@jpaulreed
We All Agree on DevOps, Right?
“Please explain to me: what exactly is DevOps?”
What We Look Like Answering…
“Uhm... so what technological capabilities will we gain if we ‘Do
DevOps?’”
What We Look Like Answering…
12
@jpaulreed
What We Look Like Answering…
“Uhm... so what technologicalcapabilities will we gain if we
‘Do DevOps?’”
13
@jpaulreed
14
@jpaulreed
Requisite Silo Photo
15
@jpaulreed
Requisite Silo Photo
Dev
elop
men
t
Ope
rati
ons
16
@jpaulreed
Requisite Silo Photo
Dev
elop
men
t
Ope
rati
ons
Prod
uct
Man
agem
ent
Sale
s/M
arke
ting
17
@jpaulreed
A Small Digression on Silos
18
@jpaulreed
Actual Silos
19
@jpaulreed
Back to Silos
20
@jpaulreed
Back to Silos
21
@jpaulreed
Back to Silos
22
@jpaulreed
“Yeeahhh... so what kind of DevOps... would you... say ya do here?”
23
@jpaulreed
What do “DevOps Teams” do? Configuration Management Continuous Integration Developing & Supporting Deployment / Pipeline Tools Dependency / Artifact Management Versioning / SCM Operations (Maybe?)
What did we used to call these things?
25
@jpaulreed
“Continuous Delivery is a Set of Principles and
Practices to Reduce the Cost, Time, and Risk of Delivering Incremental
Changes to Users.”
-Jez Humble
Continuous Delivery is your Organization— Your Entire Organization—caring about release engineering and quality assurance in a way it has never cared about them before. Ever.
- J. Paul Reed
28
@jpaulreed
Back to Silos
29
@jpaulreed
Back to Silos
30
@jpaulreed
Anyone Else Feel Like…
“I feel like I’m taking CRAZY PILLS!!”
31
@jpaulreed
PeopleCare!
34
@jpaulreed
35
@jpaulreed
Systems Thinking is a Thing™
36
@jpaulreed
Resources
37
@jpaulreed
Pain is shared
38
@jpaulreed
“[Computing] is pop culture. I'm not against pop culture. But pop culture holds a disdain for history.
Pop culture is all about identity and feeling like you're participating. It has nothing to do with cooperation, the past or the future — it's living in the present.
I think the same is true of most people who write code for money.
They have no idea where [their culture came from].”
— Alan Kay
41
@jpaulreed
42
@jpaulreed
Versioning is Fun
43
@jpaulreed
Versioning is Fun
44
@jpaulreed
Versioning is Fun
45
@jpaulreed
Versioning is Fun
46
@jpaulreed
47
@jpaulreed
48
@jpaulreed
49
@jpaulreed
50
@jpaulreed
1st Law of DevOpsDynamics
52
@jpaulreed
Visibility is Hard
53
@jpaulreed
If You Stare at this All Day
54
@jpaulreed
The best single question for testing an organization’s character is: What happens when people make mistakes?
- Robert I. Sutton
55
@jpaulreed
Sorry… No One Wants These
56
@jpaulreed
Like Uber, but for RelEng
57
@jpaulreed
The Hard Truth
58
@jpaulreed
[It’s] important to understand the strategy, the context, and the value that’s important to your organization; and then how you play into those.
- Dr. Nicole Forsgren, Chef
“Until you take the time to sit and understand that, DevOps for the sake of DevOps doesn’t matter.”
- Dr. Nicole Forsgren, Chef
60
@jpaulreed
The Cruel PunchlineThe Single Practice Correlated to Improvement in… Deployment Frequency Lead Time for Changes Mean Time to Recover
61
@jpaulreed
The Cruel PunchlineThe Single Practice Correlated to Improvement in… Deployment Frequency Lead Time for Changes Mean Time to Recover
Use of Version Control for All Production Artifacts
62
@jpaulreed
63
@jpaulreed
64
@jpaulreed
3 Weird Tricks
1. Every release engineering strategy you deploy must to be:- Complexity-informed- Accounts for the entirety of the system (systems thinking)
- Address human factors
65
@jpaulreed
Cynefin Sensemaking FrameworkComplex Complicated
Chaotic Simple
ProbeSense
Respond
SenseAnalyzeRespond
ActSense
Respond
SenseCategorizeRespond
Disorder
Emergent Good Practice
Novel Best Practice
Emergent Good Practice
Novel Best Practice
66
@jpaulreed
Cynefin Sensemaking FrameworkComplex Complicated
Chaotic Simple
ProbeSense
Respond
SenseAnalyzeRespond
ActSense
Respond
SenseCategorizeRespond
Disorder
Emergent Good Practice
Novel Best Practice
Emergent Good Practice
Novel Best Practice
67
@jpaulreed
3 Weird Tricks
1. Every release engineering strategy you deploy must to be:- Complexity-informed- Accounts for the entirety of the system (systems thinking)
- Address human factors
68
@jpaulreed
Human Factors?
69
@jpaulreed
3 Weird Tricks
2. If you[r team] is not involved in some sort of continuous improvement, you should be worried.
70
@jpaulreed
71
@jpaulreed
3 Weird Tricks
3. If you[r team] is not working on a continuous delivery pipeline, you should be worried
72
@jpaulreed
73
@jpaulreed
Bullish on Release Engineering
74
@jpaulreed
Questions?
J. Paul Reed www.jpaulreed.com Twitter: @jpaulreed
www.release-approaches.com Simply Ship. Every Time.