Blameless CI - Bashing Cultural Monsters in Continuous Integration
Does your organization frown upon “Build Breakers”? Does your team spend a lot of time fixing integration issues in CI? Do you see a lot of “Who broke the build now?” emails? Do your team members hesitate to commit their code for the fear of causing a build failure?
If you wish to know what you can do to make the situation better, this session is for you.
Continuous Integration is a powerful way to identify and eliminate certain risks, particularly when multiple teams are rallying towards a planned release. Even if you are not working on a planned release, Continuous Integration will help you to cut-out a release sooner than you would if you did not have CI.
When organizations or teams start adopting Continuous Integration for the first time, they develop an untold habit to chastise the build breaker, whenever a build breaks. Most of the time, the reprimanded build breaker is a person and not a thing, a machine or a process
Outline/Structure of the Talk
Introduction – 2 mins
Effects of Blame on Organization's Productivity - 5 mins
Developer’s Control on CI Failure - A simulation using Traffic Convergence example – 5 mins
How to drive the Culture Change with Blameless CI? – 3 mins
Simple Metrics to understand the culture change? – 3 mins
Q & A – 2 mins
Total – 20 mins
The audience will leave the session with an understanding of
- Effects of blame on effectiveness of CI
- Ideas and Techniques to avoid blame while implementing CI
- Tried and tested Metrics to build a Blameless CI culture
Developers, Testers, Scrum Masters, Project Managers, Program Managers, Agile Change Agents