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 🙂
Actually, the frequent CI build failures signal a totally different set of problems that might need intervention from higher echelons of the organization.
Introduction – 4 mins
Fear of Failure – Psychology Behind it- 5 mins
Developer’s Control on CI Failure – 6 mins
Disadvantages of the Traditional Approach – 10 mins (A Collaborative exercise using Systems Thinking model)
Culture Change – 5 mins
What can we do to prevent this? – 10 mins
Q & A – 5 mins