Continuous Delivery is more than just Tooling, It's a Mindset

So your organisation wants to implement Continuous Delivery. But is your organisation ready for this ? Does it have the right mindset ? To be successful with Continuous Delivery, you have to adopt the proper mindset as a whole organisation. Just throwing tools at it will not do the job.

Transcript

1. @tdpauw thinkinglabs.io @tdpauw thinkinglabs.io Continuous Delivery is more than just Tooling, It's a Mindset Thierry de Pauw, @tdpauw
2. @tdpauw thinkinglabs.io So you want to adopt Continuous Delivery. Where do you start ?
3. @tdpauw thinkinglabs.io RAKE
4. @tdpauw thinkinglabs.io Continuous Delivery is NOT just tooling. It is a mindset to adopt.
5. @tdpauw thinkinglabs.io Continuous Delivery done badly is like #FlaccidScrum.
6. @tdpauw thinkinglabs.io The goal of Continuous Delivery is to sustainably minimise the lead time to create positive business impact.
7. @tdpauw thinkinglabs.io The Principle of the 3 Ways • Increase Speed • Improve Stability • Culture of Improvement
8. @tdpauw thinkinglabs.io #1 - Increase Speed Maximise the flow of the software delivery process. Development Operations Customer Business
9. @tdpauw thinkinglabs.io Repeatable and reliable process for delivering software. This means • automate the hell out of it, • and everything is under version control.
10. @tdpauw thinkinglabs.io Encourage collaboration.
11. @tdpauw thinkinglabs.io Create an empowered product team.
12. @tdpauw thinkinglabs.io Aim for a single piece flow.
13. @tdpauw thinkinglabs.io Bigger batches = more WIP = more inventory = more money stuck in the system
14. @tdpauw thinkinglabs.io Bigger batches = bigger risks • Release process is more often practiced • Finding out what went wrong is easier • Rolling back small changes is easier • Roll forward a new version
15. @tdpauw thinkinglabs.io Your Definition of Done is when the feature is in the hands of the users.
16. @tdpauw thinkinglabs.io Your application is always in a releasable state on mainline. Ready for release does not mean actually releasing. Software with unfinished work can still be released. Every build is a potential release candidate.
17. @tdpauw thinkinglabs.io Trunk Based Development
18. @tdpauw thinkinglabs.io Trunk Based Development • Make changes incrementally
19. @tdpauw thinkinglabs.io Trunk Based Development • Make changes incrementally • Hide unfinished new functionality
20. @tdpauw thinkinglabs.io Trunk Based Development • Make changes incrementally • Hide unfinished new functionality • Branch by Abstraction
21. @tdpauw thinkinglabs.io Trunk Based Development • Make changes incrementally • Hide unfinished new functionality • Branch by Abstraction • Feature Toggle
22. @tdpauw thinkinglabs.io #2 - Improve Stability Creating feedback loops at all stages of the pipeline. Development Operations Customer Business
23. @tdpauw thinkinglabs.io Whenever something fails, stop the production line.
24. @tdpauw thinkinglabs.io Build quality into the code from the start, don't test it in later. 2 kinds of inspections • Inspection after the defect occurred • Inspection to prevent defects
25. @tdpauw thinkinglabs.io Testing is not a phase, it is part of your development process. Everybody is responsible for the quality.
26. @tdpauw thinkinglabs.io Move away from the Test Ice Cream Cone Unit Tests Acceptance Tests End to End Tests Manual Tests
27. @tdpauw thinkinglabs.io Continuous Testing with Test Pyramid
28. @tdpauw thinkinglabs.io Continuous Delivery works because it has this crazy focus on Quality.
29. @tdpauw thinkinglabs.io #3 - Creating a Culture of Improvement Development Operations Customer Business
30. @tdpauw thinkinglabs.io "If a system is not improving, the result is not steady state. Instead, because of entropy, organisational performance declines." -- Mike Rother, Toyota Kata: Managing People for Improvement, Adaptiveness and Superior Results
31. @tdpauw thinkinglabs.io The Improvement Kata Define a vision for your Delivery Process.
32. @tdpauw thinkinglabs.io Repetition and practice leads to mastery. If it hurts, do it more often. Bring the pain forward.
33. @tdpauw thinkinglabs.io Conclusion
34. @tdpauw thinkinglabs.io Optimising for throughput and for speed gets you to lower costs and higher quality. Where in the past optimising for cost and quality got you neither.
35. @tdpauw thinkinglabs.io Continuous Delivery is not easy nor cheap !
36. @tdpauw thinkinglabs.io Version Control Test Driven Development Automated Configuration Assume - Verify Automated Infrastructure Acceptance Test Driven Development Deployment Pipeline Consumer Driven Contracts Trunk Based Development Exploratory Testing Continuous Integration Smoke Tests Evolutionary Architecture Test Data Management Database Migrations Monitoring & Alerting Canary Deployments Required Technological Changes
37. @tdpauw thinkinglabs.io Required Organisational Changes Empowered Product Teams Everyone is On-Call Cross-Functional Teams Continuous Change Review Small Batch Sizes Traceability of Changes Shared Incentives Upskill Employees Blameless Post-Mortems Conway's Law Alignment Continuous Improvement
38. @tdpauw thinkinglabs.io “When considering an agile transformation, consider adopting Continuous Delivery because it embodies the technical heart of Agile.” -- Mary Poppendieck, Pitfalls of Agile Transformations
39. @tdpauw thinkinglabs.io @tdpauw thinkinglabs.io Hello, my name is Thierry de Pauw, @tdpauw Continuous Delivery consultant Agile Technical coach Lean and XP Software Engineer Founder of ThinkingLabs shy, introvert, opinionated dark chocolate, coffee Ghent, Belgium