Abstract: Companies that release multiple times a day typically financially outperform companies that don’t. If you have a basic deployment pipeline in place, how do you go from weekly or daily deployments to multiple times a day? The counter-intuitive answer is to break work down into small frequent source code commits and deploy these as they are committed, but doing this has an impact on how developers and testers work.
In this interactive workshop, we will be using games to introduce the concepts of small frequent commits and deployments, learn why existing developer and tester practices may create a bottleneck in the deployment pipeline, and what changes you can make to avoid these bottlenecks. The exercises run within the sessions are designed to be taken back to the office to help with coaching your co-workers.
Learning Outcomes: - Exercises to help coach, teach, or influence colleagues to adopt small frequent commits and the required technical practice changes
- The business case for adopting small frequent commits
- What is a trunk-based branching strategy and why you need to move to it
- Using Feature toggles to enable small commits and trunk-based branching strategy
- What changes do feature toggles bring to Software Testing
Attachments:
