No agility without Continous Delivery

An agile transformation without a strong focus on Continuous Delivery is non-sensical today.

CD links business value directly to the transformation and gives great protection agains falling back to business as usual

Transcript

1. 15/10/2021 No Agility without Continuous Delivery Bastien David Johan Martinsson Rémy Sanlaville
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. How about you change for business reasons? Photo by Jason Leung on Unsplash
13. And everyone will be happy Photo by Senjuti Kundu on Unsplash
14. And no, you do not need a SAFe certification
15. We suggest you add ONE small constraint to your organization Photo by Annie Spratt on Unsplash
16. Deploy to production, everyday
17. And that’s it
18. Yep, that’s it
19. Now… why is it worth it?
20. Gain customers by offering them what they need sooner
21. Build confidence with our customers Photo by Austin Kehmeier on Unsplash
22. Seize opportunities Photo by Charlene on Unsplash
23. Less emergencies Photo by Axel Bertrand on Unsplash
24. Reduce the need for coordination Photo by Joseph Benson-Aruna on Unsplash
25. Invest less in uncertainty
26. Autonomy, mastery and purpose for the teams
27. And yes it’s tough Photo by Grant Durr on Unsplash
28. And you will grow while trying to achieve this Photo by Chetan Kolte on Unsplash
29. No BS, it really works Photo by Anastasiia Rozumna on Unsplash
30. Have you read this book?
32. What makes a transformation successful?
33. System thinking
34. Every (long lived) system is stable
35. Every (long lived) system is stable
36. Every (long lived) system is stable
38. No tooling Habits
39. No tooling Habits
40. Deliver more 
 often No tooling Habits
41. Deliver more 
 often No tooling Practice Habits
42. Deliver more 
 often No tooling Practice Smaller, yet 
 useful features Habits
43. Deliver more 
 often No tooling Practice Smaller, yet 
 useful features Habits
44. Good practices will emerge from this constraint Photo by Annie Spratt on Unsplash
45. Reveal the problems to prioritize them
46. But is it a good idea to expose the problems?
47. https://antifragile.fr
48. And once you know how to deliver several times a day… Photo by Jon Tyson on Unsplash
49. You will have become agile without even realizing it…
50. While offering your company opportunities and a competitive advantage Photo by Jon Tyson on Unsplash
51. Beware of the traps along the way Photo by Tom Barrett on Unsplash
52. Trunk based development over Feature branches Photo by Eugene Chystiakov on Unsplash
53. • FB seems like a good solution until you know how code so that any intermediate commit can go into production Trunk based development over Feature branches Photo by Eugene Chystiakov on Unsplash
54. • FB seems like a good solution until you know how code so that any intermediate commit can go into production • Feature branching is accidental complexity Trunk based development over Feature branches Photo by Eugene Chystiakov on Unsplash
55. • FB 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 your con fi g with git branching? So why are you? Trunk based development over Feature branches Photo by Eugene Chystiakov on Unsplash
56. Fix it over Rollback Photo by ThisisEngineering RAEng on Unsplash
57. Automation over Gatekeeping Photo by Lenny Kuhne on Unsplash
58. Removing the problem over Tackling it Photo by Ujesh Krishnan on Unsplash
59. TBD over Feature branches Fix it over Rollback Automation over Gatekeeping Removing the problem over Tackling it Photo by Cesar Cid on Unsplash
60. What you’ll see and hear if you decide to give it a go Photo by Yang Shuo on Unsplash
61. More collaboration Photo by krakenimages on Unsplash
62. More quality Photo by Manuel Cortina on Unsplash
63. More automation Photo by David Levêque on Unsplash
64. Less stock Photo by Adrian Sulyok on Unsplash
65. Less waste Photo by Pawel Czerwinski on Unsplash
66. More responsiveness Photo by israel palacio on Unsplash
67. More stability #antifragile Photo by Christophe Hautier on Unsplash
68. In a word, agility 😉
69. Deploy to production, everyday
70. So, when do you start? Photo by Brett Jordan on Unsplash