Avoid superfluous synchronization and other kinds of waste by Continuous Delivery Continous delivery is proven efficient and contrary to scrum and many other agile methods, it's "pulls" great technical practices Trunk based development

1. 24/11/2021
No Agility without
Continuous Delivery
Bastien David
Johan Martinsson
Rémy Sanlaville
Agile Grenoble

2. Who is working in
an agile project?
Photo by İrfan Simsar on Unsplash

3. Really?
Photo by Ignacio Amenábar on Unsplash

4. So you can deploy to
production several
times a week!?
Photo by Ralph (Ravi) Kayden on Unsplash

5. An agile transformation: why?
Photo by Ana Municio on Unsplash
150 pt

6. We have SO many wrong
reasons to do it
Photo by krakenimages on Unsplash

7. It’s trendy
Photo by Joshua Chun on Unsplash

8. Top management asked for it
Photo by Roland Samuel on Unsplash

9. HR needs something to show for
Photo by Wesley Tingey on Unsplash

10. As a manager it’s my role to
change the organisation
Photo by iMattSmart on Unsplash

11. We heard some people were
unhappy
Photo by Clem Onojeghuo on Unsplash

12. And it’s so easy to get it wrong
Photo by Jelleke Vanooteghem on Unsplash

13. Long-lived branches
Photo by Ivan Aleksic on Unsplash

14. Teams synchronisation
Photo by Rainier Ridao on Unsplash

15. Silos
Photo by Waldemar Brandt on Unsplash

16. Photo by Aaron Burden on Unsplash
Release freeze

17. Manual testing
Photo by Jeswin Thomas on Unsplash

18. Not fetching user feedback
Photo by Davyn Ben on Unsplash

19. No technical excellence
Photo by Hunter Haley on Unsplash

20. Where are we headed?
Photo by Je
ff
rey Dungen on Unsplash

21. How about we get
back to the reasons
why we started agility?
Photo by Jon Tyson on Unsplash

22. This will benefit the business
Photo by Jason Leung on Unsplash

23. And everyone will
be happy
Photo by Senjuti Kundu on Unsplash

25. We suggest you add ONE small
constraint to your organization
Photo by Annie Spratt on Unsplash

26. Deploy to production, everyday

27. And that’s it

28. Yep, that’s it

29. Now… why is it worth it?

30. Gain customers by offering them
what they need sooner

31. Build confidence
with our
customers
Photo by Austin Kehmeier on Unsplash

32. Seize opportunities
Photo by Charlene on Unsplash

33. Less emergencies
Photo by Axel Bertrand on Unsplash

34. Reduce the
need for
coordination
Photo by Joseph Benson-Aruna on Unsplash

35. Invest less in uncertainty

36. Autonomy, mastery and purpose
for the teams

37. And yes it’s tough
Photo by Grant Durr on Unsplash

38. And you will grow
while trying to
achieve this
Photo by Chetan Kolte on Unsplash

39. No BS, it really
works
Photo by Anastasiia Rozumna on Unsplash

40. Have you read this
book?

42. What makes a transformation
successful?

43. System thinking

44. Every (long lived) system is stable

45. Deliver more
often
No tooling
Practice
Smaller, yet
useful features
Habits

46. Good practices will emerge
from this constraint
Photo by Annie Spratt on Unsplash

47. Reveal the problems to prioritize
them

48. But exposing the problems
comes with a cost, no?

49. https://antifragile.fr

50. And once you know
how to deliver
several times a day…
Photo by Jon Tyson on Unsplash

51. You will have become agile
without even realizing it…

52. While offering your company opportunities
and a competitive advantage
Photo by Jon Tyson on Unsplash

53. Beware of the
traps along the
way
Photo by Tom Barrett on Unsplash

54. Fix it over Rollback
Photo by ThisisEngineering RAEng on Unsplash

55. Automation over Gatekeeping
Photo by Lenny Kuhne on Unsplash

56. Removing the
problem over
Tackling it
Photo by Ujesh Krishnan on Unsplash

57. • Feature branching seems like a good
solution until you know how code so that
any intermediate commit can go into
production
• Feature branching is accidental complexity
• Would you handle an « if » with git
branching? So why are you?
Trunk based
development over
Feature branches
Photo by Eugene Chystiakov on Unsplash

58. How?
• Instead of breaking things, introduce a
new version of the change
• Keep both versions as long as the old is
used
• Remove the old one once it is no longer
used Code
Client
New Code
Other code

59. Add new route
Duplicate existing
code and tests
Change behavior
Remove old code
…
Change an existing route
Add feature
fl
ag
Add “if"
Code
Demo on staging
Activate feature
Add new feature in front
…
Remove feature
Code

60. Decoupling over synchronisation
Photo by Malachi Brooks on Unsplash

61. Fix it over Rollback
Automation over Gatekeeping
Removing the problem over Tackling it
TBD over Feature branches
Decoupling over Synchronization
Photo by Cesar Cid on Unsplash

62. Photo by Brett Jordan on Unsplash
No way you can achieve this
without technical excellency

63. And here is how to go beyond
Photo by Brian Wangenheim on Unsplash

64. Our ideas
Our product in
production

65. What you’ll see and
hear if you decide
to give it a go
Photo by Yang Shuo on Unsplash

66. More collaboration
Photo by krakenimages on Unsplash

67. More quality
Photo by Manuel Cortina on Unsplash

68. More automation
Photo by David Levêque on Unsplash

69. Less stock
Photo by Adrian Sulyok on Unsplash

70. Less waste
Photo by Pawel Czerwinski on Unsplash

71. More responsiveness
Photo by israel palacio on Unsplash

72. More stability #antifragile
Photo by Christophe Hautier on Unsplash

73. In a word, agility 😉

74. Deploy to production, everyday

75. Agility without CD?
🤔

76. Help us to get better!