This is part of a series of posts I would like to write regarding practical techniques I have learnt, read about and used in Agile Software Development.
The main goal of this practice is to keep the snake small.
The Waste Snake feeds on tasks that are not relevant to the current agreed Iteration Goal. He is just delighted when people get interrupted and forced to enbark on another 3 hours unscheduled meeting or an apparently vital tasks that need to be done immediately because the world starvation depends on them!
Jokes apart, the rules are very simple:
- Get a deck of blank 3' x 5' index cards and make it accessible to the team.
- Everytime a team member gets interrupted, he/she will write on an index card the motive of the interruption and the time spent on it.
- He/She will add the index card to the waste snake on the wall.
I found it to be a very powerful tool especially in Retrospective meetings as it is a way to record interruptions that de-focused the team from the goal of the iteration.
It is also a really good way to find out if there are repetitive tasks that continuously interrupt the team during iterations.
An example would be:
This is a simplistic example, there are others which could include unexpected things like a Dev machine blowing up, the CI server getting stuck, an online tool your teams relies on being down.
This is what a waste snake would look like:
Feel free to download the snake head and tail and use it on your wall!
Here's the link to a PDF file with the images: Waste Snake