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

1 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

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

Learning Outcome

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

Target Audience

Developers, Testers, Scrum Masters, Project Managers, Program Managers, Agile Change Agents

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Submission
  • Joel Tosi
    By Joel Tosi  ~  1 year ago
    reply Reply

    Hi Vivek,

       I like the intent of this session and it looks like you have delivered it before.  I see a nice simulation.  I am a little concerned at 45 minutes this will feel like it has enough impact and not drawn out.  What would happen if you cut it to 20 minutes?




    • Vivek Ganesan
      By Vivek Ganesan  ~  1 year ago
      reply Reply

      Hi Joel,

      I have updated the time to 20 minutes now. Please let me know if it is okay.

    • Vivek Ganesan
      By Vivek Ganesan  ~  1 year ago
      reply Reply

      Thanks for your feedback, Joel!

      I can certainly cut it to 20 minutes and cover just the simulation part & metrics part without touching much on negative effects of blame.

      Would that be good?

  • Prasad
    By Prasad  ~  1 year ago
    reply Reply

    I think this is in the similar lines on what you proposed for another track..  With out demo, a game and working examples, we cant excite audience