Download to read offline
More Related Content
Similar to The Journey to Continuous Delivery
The Journey to Continuous Delivery
- 1. The Journey to Continuous Delivery 2Dec. 2020
- 2. Presented By & Introduction It'san initiative for gathering people interested in Agile, eXtreme Programming (aka: XP), Scrum, Coding, etc. The Idea of XP Days was found at November 2019 and since that we have conducted lots of knowledge sharing meetups and webinars. Agile Arena is an Agile Consulting and Training company. We specialize in agile adoption and transformation for companies and teams through: ⢠Designing their agile adoption programs ⢠Executing our programs and guiding the team through their journey to sustainable agility . ⢠We also provide training for teams and individuals to help them coping with the agility trend in the market.
- 3. This Webinar is HeldBy: Hesham Amin Principal Developer Class Ltd.
- 4. Presented By & AGENDA ďŹChallenges of building software. ďŹ Why is software delivery painful. While it shouldn't ďŹ Agile as a continuous experimentation process ďŹ Continuous delivery and feedback loops ďŹ Principals of Continuous delivery ďŹ Implementation of Continuous delivery ďŹ Impact on software architecture ďŹ Impact on teams ďŹ Discussion
- 5. Presented By & Challengesof Software Development
- 6.
- 7. Presented By & Uncertainty ďŹâSoftware is easy to make, except when you want it to do something new. And then, of course, there is a corollary: The only software that's worth making is software that does something new.â Scott Rosenberg, Dreaming in Code ďŹ A startup is a human institution designed to create a new product or service under conditions of extreme uncertainty.â Eric Ries ďŹ Unlike when building a house, when it comes to software it's almost impossible to know what you want. And even if you did know, it would be impossible to know how long each part would take to do. Patrick Gleeson, Working with Coders: A Guide to Software Development for the Perplexed Non-Techie
- 8. Presented By & Uncertainty ContinuousDelivery End Uncertainty Means Uncertainty
- 9. Presented By & Mindsetchange Experimentation!
- 10. Presented By & Thescientific method The scientific method Hypothesis Design an experiment Carry on the experiment Evaluat e
- 11. Presented By & FastFeedback
- 12. Presented By & Delayeddelivery of value Tim e Valu e R1 R2 R3 R4 Lost value
- 13. Presented By & ExecutionChallenges ďŹ Humans make mistakes! ďŹ Deployment âdramaâ ďŹ Long Cycle time ď Not enough experimentation ď Lack of innovation ďŹ Non value-adding activities
- 14. Presented By & Whatis Continuous Delivery The ability to get changes of all types into production, or into the hands of users, safely and quickly in a sustainable way.
- 15. Presented By & Agilemanifesto ďŹ Working software over comprehensive documentation ďŹ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. ďŹ Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. ďŹ Working software is the primary measure of progress.
- 16. Presented By & Howquick? ďŹ Mean time between deployments: ďŹ 11.6 Seconds ďŹ Max. deployments in a single hour: ďŹ 1079 ďŹ Mean number of hosts simultaneously receiving a deployment ďŹ 1000 ďŹ ďŹ 30 Deployments per day ďŹ 200+ People ďŹ 10000 deployments in 2011
- 17. Presented By & ContinuousDelivery is a... ďŹ Holistic approach to SW development ďŹ The whole value chain ďŹ Shortest path from business idea to customer value
- 18. Presented By & Feedbackcycles Pairing TDD Continuous Integration Production monitoring
- 19. Presented By & Principlesof Continuous Delivery ďŹ Build quality in. ďŹ Work in small batches ďŹ Computers perform repetitive tasks, people solve problems ďŹ Relentlessly pursue continuous improvement ďŹ Everyone is responsible
- 20.
- 21. Presented By & Implementationof Continuous Delivery ďŹ Repeatable, reliable process for releasing software ď Computers perform repetitive tasks, people solve problems ďŹ Automate almost everything ď Static analysis ď Test ď Infra ď Deployment
- 22. Presented By & Implementationof Continuous Delivery ďŹ Keep (Almost) Everything under source control ďŹ Trunk based development ďŹ Trunk is always deployable ď Check in to trunk at least daily Trunk Feature / Task
- 23. Presented By & Implementationof Continuous Delivery ďŹ If it hearts, do it more often ď âIf releasing is hard, people will always find a reason not to release.â ďŹ Gereon Hermkes, Scaling Done Right: How to Achieve Business Agility with Scrum@Scale and Make the Competition Irrelevant ďŹ Everybody is responsible for the release process ď Visibility
- 24. Presented By & Process- Deployment pipeline VCS TDD CI Build + automated tests Artifact repo Acceptance testing (automated) Component Performance Testing Production + APM System Performance Testing Manual Testing Staging
- 25.
- 26. Presented By & Impacton Architecture ďŹ Quality attributes: meet cross functional requirements ďŹ Availability: ď Rolling deployment ď Stateless when possible ď DB replicas ďŹ Deployability ďŹ Asynchronous architecture ďŹ Caching & invalidation
- 27. Presented By & Impacton Architecture ďŹ Donât break your clients. Including internal clients ď API versions ď Consumer driven contract testing ďŹ Try to avoid orchestrated deployments
- 28. Presented By & Impacton Architecture ďŹ Configurations are stored on the environment ď Environment variables ď Parameters / secrets store ďŹ Observability ď Logs ď Metrics ď APM
- 29. Presented By & Patternsof Continuous Delivery ďŹ Expand/Contract: ď Add new stuff first then remove old versions: ďŹ New static content ďŹ New API version ďŹ Expanded DB schema ď Then deprecate old ones ďŹ Blue-Green deployments ď Also a great test for DR ďŹ Deployment != Release ď Feature toggles ďŹ Canary releasing: ď Slowly rolling out the change to a small subset of users before rolling it out to the entire infrastructure and making it available to everybody
- 30. Presented By & Teamstructure ďŹ Narrow focused teams with clear responsibilities ď Features / not layers ďŹ Cross-team collaboration is usually harder ďŹ You build it â you own it/run it.
- 31. Presented By & Noend state
- 32.
- 33. Presented By &ContinuousDelivery DISCUSSION