Presented at the KZA webinar "Software Development in the Modern Age" in March 2022

1. bertjan@openvalue.eu
Better software, faster.
Principles of Continuous Delivery and DevOps
Bert Jan Schrijver
@bjschrijver

2. Software delivery in the old days…

3. Definitions
Every change goes through the
build/test pipeline and
automatically gets put into
production.
Continuous Deployment
?!
DevOps
Building and testing software in
such a way that the software can be
released to production at any time.
"Ship early, ship often, sacrificing
features, never quality" - Kyle Neath
Continuous Delivery
Team members integrate their
work frequently. Commits are
verified by automated builds
and tests.
Continuous Integration
Who’s who in CI & CD
@bjschrijver

4. What is the goal of CD?

5. a repeatable, reliable process
for releasing software
What is the goal of CD?

6. Principles
of Continuous Delivery
@bjschrijver
Build quality in
Keep everything in version control
Continuous improvement
Automate (almost) everything
Everybody is responsible
for the delivery process
Done means released
If it hurts, do it more often

7. Ingredients
03
Build & deploy
Information & reporting
05
Design & architecture
02
Culture & organisation
01
Test & verification
04
of Continuous Delivery
@bjschrijver

8. WORKED FINE IN DEV
OPS PROBLEM NOW
Continuous Delivery vs. DevOps

9. DevOps: a definition
Development and operations engineers
being responsible together
for the entire lifecycle of a product.

10. :
building and running better-quality software
more quickly and more reliably.
Developers and other IT professionals
working together on a shared goal
DevOps: another definition

11. DevOps: another definition ;-)
A set of practices intended to reduce
the time between committing a change
to a system and the change being
placed into production, while ensuring
high quality.

12. Why DevOps?
as an enabler for Continuous Delivery, faster problem
resolution and focus on value instead of problems.
DevOps makes your business move faster

13. Why DevOps?
DevOps is not about doing something new.
It’s about fixing a mistake from the past.

14. Principles
of DevOps
@bjschrijver
Continuous improvement
Automation
Ownership
Experimentation
Gradual changes
Customer oriented
Collaboration

15. The DevOps disaster
15 ways to fail at DevOps

16. DevOps is the same thing as
Continuous Delivery and Continuous Deployment
It’s not. We just talked about this ;-)
Failure 1

17. You need a central ‘DevOps team’
that handles all ops stuff
Source: http://www.nasa.gov/images/content/218652main_STOCC_FS_img_lg.jpg
No. DevOps is about removing silos, not about adding more.
Failure 2

18. DevOps is only for
development and operations engineers
No. Everyone in the team is in. Testers too!
Failure 3

19. DevOps means
developers managing production
WORKED FINE IN DEV
OPS PROBLEM NOW
No. Yes. It depends ;-)
Failure 4

20. DevOps is only for
hipsters, startups and unicorns
Source: http://attitudes4innovation.com/wp-content/uploads/2014/04/3683.Nubis_Team_May_2013.jpg
No. DevOps can work for the enterprise, too.
Failure 5

21. You need containers, microservices
and ‘the cloud’ to do DevOps
Source: http://www.matrixfans.net/wp-content/uploads/2011/10/spoon-boy.jpg
THERE IS NO CLOUD
IT’S JUST SOMEONE ELSE’S COMPUTER
No. DevOps is not about technology. It’s about collaboration.
Failure 6

22. DevOps is about
automation
No. Well, automation helps, but it’s not the main goal of DevOps.
Failure 7

23. DevOps is about
tools
No, you don’t need Chef or Puppet to do DevOps.
Failure 8

24. DevOps is a job title -
something you can be certified in
Source: http://blog.mrii.org/wp-content/uploads/2015/10/certified.png
No. Noooo! Just no. Or actually: yes. You’re all certified!
Failure 9

25. DevOps replaces
Agile
Source: http://blogs.metageek.net/wp-content/uploads/2015/04/IMG_6967-1024x768.jpg
No. Agile is a way to develop software. DevOps has a broader goal.
Failure 10

26. DevOps doesn’t work with
waterfall, Prince or ITIL
Source: http://www.thewallpapers.org/photo/30981/4-3-2-waterfall.jpg
No. That’s like saying “collaboration doesn’t work with …”
Failure 11

27. You don’t need to define
what DevOps means to your organisation
Source: https://headguruteacher.files.wordpress.com/2013/02/screen-shot-2013-02-12-at-22-26-37.png
No. You really really need to. Trust me. I didn’t and I regret it.
Failure 12

28. You can do DevOps
without management buy-in
Source:http://cdn.ttgtmedia.com/visuals/ComputerWeekly/Hero%20Images/IT-management-CIO-fotolia.jpg
No. Changing an organisation requires C-level support.
Failure 13

29. You can enforce DevOps
in an organisation
Source: https://www.all4shooters.com/de/Bildergalerien/Pro-Zone/Enforce-Tac-2016
No. You can never enforce cultural change.
Failure 14

30. DevOps prevents
failure
Photo: Andres Harambour
No. DevOps embraces failure. Failure is where you learn.
Failure 15

31. What is DevOps really about?

32. DevOps is about culture
Source: http://www.azmc.org/wp-content/uploads/2012/11/Arts-and-Culture-Large.jpg

33. DevOps is about freedom and responsibility
Source: https://images.unsplash.com/photo-1449177009399-be6867ef0505

34. DevOps is about empathy
Source: http://www.scarymommy.com/wp-content/uploads/2014/06/empathy.jpg

35. That sounds great,
but it won’t work here
“
”
Photo: Dave Lehl, text source: Jez Humble

36. “Continuous Delivery won’t work here”
• Stated reasons:
• we’re regulated
• we’re not building
websites
• too much legacy
• our people are too
stupid
• Actual reasons:
• our culture stinks
• our architecture
stinks
Photo: Dave Lehl, text source: Jez Humble
Source: talk by Jez Humble
https://www.youtube.com/watch?v=837Z_oehhRg

37. Why should I do all this?

38. Why CD & DevOps?
• Reducing errors
• Lowering stress
• Empowering teams
• Deployment flexibility
• Practice makes perfect

39. Source: https://7216-presscdn-0-76-pagely.netdna-ssl.com/wp-content/uploads/2011/12/confused-man-single-good-men.jpg
Where do I get started?

40. …said no product manager ever.
J. Paul Reed
Let’s spend the next few months..
..working on automated testing and build/release
infrastructure, and redesigning how our application is
written. We can postpone our feature development.
“
”

41. Take one thing you’re pretty
sure you can improve.
Start small
Tackle the next issue
and keep improving!
Iterate
Approach
How to spark change
When done, share the results
with your team.
Celebrate!
Show results
@bjschrijver

42. Summary

43. What is the goal of a software team?

44. Working, useful software,
in production.

45. Source: https://cdn2.vox-cdn.com/thumbor/J9OqPYS7FgI9fjGhnF7AFh8foVY=/148x0:1768x1080/1280x854/cdn0.vox-cdn.com/uploads/chorus_image/image/46147742/cute-success-kid-1920x1080.0.0.jpg
THAT’S IT.
NOW GO KICK SOME ASS!

46. Questions?
@bjschrijver

47. Thanks for your time.
Got feedback? Let me know!
All pictures belong
to their respective
authors
@bjschrijver