Who is ideally responsible for repairing a Continuous Integration build that failed?

The responsibility for repairing a Continuous Integration build that has failed ideally falls to the person who broke the build. This aligns with the principle of accountability in Scrum and encourages a culture of ownership and responsibility within the Development Team. When a team member introduces an error that leads to a build failure, they are generally in the best position to understand the context of their changes, identify the root cause of the failure, and implement a fix.

This approach not only promotes individual accountability but also fosters a collaborative atmosphere where team members are motivated to support each other in maintaining the integrity of the codebase. It helps establish a shared understanding of quality and encourages developers to be more careful in their work, knowing that they will need to address any issues they create.

Repairing the build is not typically the responsibility of the Scrum Master or the Product Owner, as their roles focus more on facilitation, support, and prioritization rather than direct involvement in the technical aspects of development work. The Development Team as a whole does have a collective responsibility for the code quality, but highlighting individual accountability helps drive a culture of ownership that is essential for effective team dynamics in agile practices.