The document discusses the evolving role of release engineering within a DevOps framework, highlighting the importance of collaboration, continuous delivery, and quality assurance in software development. It underscores the need for organizations to adopt a systems-thinking approach, account for human factors, and maintain continuous improvement to effectively implement DevOps practices. Additionally, it stresses that embracing these methodologies is a unique journey for each organization, emphasizing the significance of understanding the contextual needs of the business.

1. THE
CHANGING
ROLE OF
RELEASE
ENGINEERING IN A
DEVOPS WORLD
J. Paul Reed
Managing Partner

2. 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”
@jpaulreed

3. A LITTLE SURVEY...
@jpaulreed

4. BACK IN THE DAY
Humble
Beginnings
as a
Build/Release
Monkey...
@jpaulreed

5. BACK IN THE DAY
@jpaulreed

6. SHIPPIN’ BITS
@jpaulreed

7. “Yeeahhh... so what would you...
say ya do here?”
@jpaulreed

8. THE ELEPHANT IN THE ROOM
@jpaulreed

9. WE ALL AGREE ON DEVOPS, RIGHT?
@jpaulreed

10. WHAT WE LOOK LIKE ANSWERING...
Please explain to me:
what exactly is DevOps?
@jpaulreed

11. WHAT WE LOOK LIKE ANSWERING...
Please explain to me:
what exactly is DevOps? @jpaulreed

12. WHAT WE LOOK LIKE ANSWERING...
Ok, what specific things
would we do to get
DevOps “tools & culture?”
@jpaulreed

13. WHAT WE LOOK LIKE ANSWERING...
Ok, what specific things would we do to
get DevOps “tools & culture?”
@jpaulreed

14. WHAT WE LOOK LIKE ANSWERING...
Uhm... so what technological
capabilities will we gain if we
“Do DevOps?”
@jpaulreed

15. WHAT WE LOOK LIKE ANSWERING...
Uhm... so what technological
capabilities will we gain if we “Do DevOps?”
@jpaulreed

16. @jpaulreed

17. REQUISITE SILO PHOTO
@jpaulreed

18. REQUISITE SILO PHOTO
Development
Operations
@jpaulreed

19. REQUISITE SILO PHOTO
Development
Operations
Product
Management
Sales/Marketing
@jpaulreed

20. A SMALL DIGRESSION ON SILOS...
@jpaulreed

21. ACTUAL SILOS
@jpaulreed

22. BACK TO SILOS
Dev
Ops
@jpaulreed

23. BACK TO SILOS
Dev
Ops
@jpaulreed

24. BACK TO SILOS
Dev
Ops
@jpaulreed

25. BACK TO SILOS
Dev
Ops
DevOps
@jpaulreed

26. “Yeeahhh... so what kind of DevOps...
would you... say ya do here?”
@jpaulreed

27. •Configuration Management
•Continuous Integration
•Developing & Supporting Deployment / PipelineTools
•Dependency / Artifact Management
•Versioning / SCM
•Operations (Maybe?)
WHAT DO “DEVOPS TEAMS” DO?
@jpaulreed

28. What did we used
to call these things?
@jpaulreed

29. @jpaulreed

30. NOTES:
• This can be u
quotations, tes
tweets, etc.
• Move the quo
marks depend
your text length
appears like th
example
• Also move th
attribution dep
text lenth so th
this example
Continuous Delivery Is A Set Of Principles And
Practices To Reduce The Cost, Time, And Risk Of
Delivering Incremental Changes To Users.
-Je z Humble
@jpaulreed

31. 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
@jpaulreed

32. BACK TO SILOS
Dev
Ops
DevOps
@jpaulreed

33. BACK TO SILOS
Dev
Ops
Release
Engineering
@jpaulreed

34. ANYONE ELSE FEEL LIKE...
@jpaulreed

35. @jpaulreed

36. @jpaulreed

37. People
Care!
@jpaulreed

38. @jpaulreed

39. SYSTEMS THINKING IS A THING™
@jpaulreed

40. RESOURCES!
@jpaulreed

41. PAIN IS SHARED
@jpaulreed

42. @jpaulreed

43. @jpaulreed

44. “[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
@jpaulreed

45. @jpaulreed

46. VERSIONING IS FUN
@jpaulreed

47. VERSIONING IS FUN
@jpaulreed

48. VERSIONING IS FUN
@jpaulreed

49. VERSIONING IS FUN
@jpaulreed

50. @jpaulreed

51. @jpaulreed

52. @jpaulreed

53. @jpaulreed

54. 1ST LAW OF DEVOPSDYNAMICS
@jpaulreed

55. WELCOME ABOARD THE SS DOCKER!
@jpaulreed

56. @jpaulreed

57. VISIBILITY IS HARD
@jpaulreed

58. IF YOU STARE AT THIS ALL DAY...
@jpaulreed

59. The best single question
for testing an
organization’s character is:
What happens when
people make mistakes?
-Robert I. Sutton
@jpaulreed

60. SORRY... NO ONE WANTS THESE
@jpaulreed

61. LIKE UBER, BUT FOR RELENG
@jpaulreed

62. THE HARD TRUTH
@jpaulreed

63. [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
@jpaulreed

64. Until you take the time to
sit and understand that,
DevOps for the sake of
DevOps doesn’t matter.
— Dr. Nicole Forsgren, Chef
@jpaulreed

65. THE CRUEL PUNCHLINE…
•Deployment Frequency
•Lead Time for Changes
•Mean Time to Recover
The Single Practice
Correlated to
Improvement in…
@jpaulreed

66. THE CRUEL PUNCHLINE…
•Deployment Frequency
•Lead Time for Changes
•Mean Time to Recover
The Single Practice
Correlated to
Improvement in…
Use of Version Control for All Production Artifacts
@jpaulreed

67. @jpaulreed

68. @jpaulreed

69. 3 WEIRD TRICKS
•Complexity-informed
•Accounts for the entirety of the
system (systems thinking)
•Address human factors
1. Every release engineering strategy
you deploy must to be:
@jpaulreed

70. CYNEFIN SIDEBAR
@jpaulreed

71. CYNEFIN SIDEBAR
@jpaulreed

72. CYNEFIN SIDEBAR
@jpaulreed

73. 3 WEIRD TRICKS
•Complexity-informed
•Accounts for the entirety of the
system (systems thinking)
•Address human factors
1. Every release engineering strategy
you deploy must to be:
@jpaulreed

74. HUMAN FACTORS?
@jpaulreed

75. HUMAN FACTORS?
@jpaulreed

76. 3 WEIRD TRICKS
2. If you[r team] is not
involved in some sort of
continuous improvement,
you should be worried.
@jpaulreed

77. @jpaulreed

78. 3 WEIRD TRICKS
3. If you[r team] is not
working on a
continuous delivery pipeline,
you should be worried.
@jpaulreed

79. @jpaulreed

80. BONUS TRICK!
4. Find allies!
(There are some weird
ones out there these
days!)
@jpaulreed

81. H O W D O T H E Y
I N T E R S E C T ?
R E L E A S E E N G I N E E R I N G
A N D
R U G G E D D E V O P S :
@jpaulreed

82. @petecheslock
DevOps
Sec
@hijinksensue(via @petecheslock) @jpaulreed

83. One vulnerable library
in your product
is a security problem.
Multiple copies of a vulnerable library
in your product
is a release engineering problem.
— @jpaulreed
@jpaulreed

84. One vulnerable library
in your product
is a security problem.
Multiple versions of a vulnerable library
in your product
is a release engineering problem.
— J. Paul Reed

85. BULLISH ON RELEASE ENGINEERING
@jpaulreed

86. J. Paul Reed
www.jpaulreed.com
@jpaulreed
www.release-approaches.com
Simply Ship. EveryTime.

87. Adoption of Agile
& DevOps
methodologies is a
journey, and every
person and
organization’s
journey is going to
be different.
-J. Paul Reed
DevOps
inPractice
J. Paul Reed
http://jpaulreed.com/devops-in-practice
@jpaulreed