Stop the line

One of the common examples of “Stop the line” principle is, the usage of continuous integration in the agile world. Continuous integration, halts a build if there are test failures. And the onus is on the team to fix it immediately. The problem we have, is addressing bugs that were reported by testers as soon as possible. We also want to build a culture of zero tolerance to bugs. How do we incorporate this into our daily work cycle?

Recently we started conducting our daily scrum by using the order of the user stories on the board. Instead, of going round the room; we run through the task board, top to down and anyone working on the story will provide their updates (answering the 3 questions pertaining only to that user story). Sounds interesting? – Here’s a blog post on the subject by Mike Cohn.

To highlight the fact that we do not want to tolerate bugs, the testers prioritized the bugs as the highest item in the iteration backlog. So during daily scrum, when the team runs through the board top to down, the bugs are first thing that the team needs to address. Although, we have not gotten to addressing bugs as soon as we find it, we now ensure that we deal with them every day.

vinod
About

Recovering programmer, Agile software developer & coach

Posted in Agile, Lean Tagged with: ,

Leave a Reply

Your email address will not be published. Required fields are marked *

*

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: