Joe Arnold - Latest Comments in Kanban: “Just set it and forget it!”

Re: Kanban: “Just set it and forget it!”

Joe Arnold — Thu, 19 Jun 2008 11:35:07 -0000

How they handle releases is to create buckets that live in the 'done' column. Sometimes when something hits the done column it needs to be deployed immediately (like an emergency bug fix). Sometimes the team is working on two different products at the same time. The team uses different colored post-it notes for each product. Each product has its own bucket where features/bug fixes congregate -- waiting for the next release for that product. As for the 'activities related to a release' task. I don't think they create another 'thing to do' that works its way through the kanban system. When it's time, I think the team just re-evaluates everything in that bucket before launch.

Re: Kanban: “Just set it and forget it!”

Chris Newman — Wed, 18 Jun 2008 17:08:54 -0000

Very nice - simple and transparent. One question - how are they handling releases - just another item in the 'things to do' queue?

Re: Kanban: “Just set it and forget it!”

Joe Arnold — Thu, 05 Jun 2008 02:10:04 -0000

That's one option. Usually what this team does is leave it in 'test'. The developer works with the tester to fix it. This is the 'stop-the-line' mentality of bug fixing. If a bigger issue comes up, then another ticket is created and is prioritized by the product manager. There are a couple of other possibilities too. Check out my post on 'What to do with bugs when using Kanban'
http://joearnold.com/2007/1...

Re: Kanban: “Just set it and forget it!”

Anonymous — Wed, 04 Jun 2008 23:54:05 -0000

When a tester discovers a bug in a "dev done" item what happens? does it move back into the "under development" column?