The Blog
Building a Kanban board
published March 10, 2011
We have been using Scrum in my current project from the beginning of 2010. Our team is swarming pretty effectively on tasks and we decided that next step would be to try out Kanban as we are currently in “production” mode and see the end of our project closing.
I started this process by reading Kanban book by David J. Anderson which I highly recommend. In his book, David suggest that transition to Kanban should be started small and from the area of team’s “political control”. Board should be designed to fit current process and team should not try to optimize process prematurely. In addition, we knew that in our case input to the Kanban system would be a Scrum backlog. Armed with this information we started to sketch first the version of our board.
Sketching the version one
Layout of your Kanban board will depend on your current situation. There isn’t one right layout and people doing the work will have the best knowledge. We started by sketching our current process and thinking what classes of services we would be providing. Classes of services are basically priorities that will be assigned to kanbans so that critical work can cut in line. In our case, we decided to build 2-tier board, where “larger” cards represent user stories and “smaller” cards represent tasks. Apparently, the best practice (or at least some practice) seems to be that user stories are limited by swimlanes and their tasks are limited by “vertical WIP”. Sounds awful but bear with me.
Get some supplies
After initial board was sketched I headed to bookstore to get some tape and post-its in different colors. I tried to find very narrow black tape, but there was no such thing available so instead I bought some electricity tape and a box cutter.
Building the version one
First things first. kanban systems came from Toyota where 5s (Sorting, straightening, shining, standardizing, sustaining) methodology originated. In our case we decided to do something to our “not so shining” whiteboard.
Because I did not find any narrow tape I used a box cutter to slice tape to more stripes.
This turned out to be a bad choice. Surprisingly, I could not do completely straight slices and almost cut my fingers into half. Next time I will find proper sized tape. Anyhow, our board started to build up. Different colored tape turned out to be a good choice. Below you can see the magical metamorphosis.
And so was first version completed.
So how does this board work?
This Kanban board is designed for a four person team, who has been working with Scrum. Work will be pulled into system from product backlog that is handled by a product owner. The team will then develop features after which they are verified by a product owner or someone from business. After verification, the team is responsible for production deployment. Currently, we favor smaller user stories and layout is designed that in mind.
Click on image below to see larger description how our first version works.
Stay tuned!
This is my first attempt to do a Kanban board and there will surely be something to fix. First thing that we will be checking is our WIP limits. Cannot wait to try how this works in practice…
2 Comments to Building a Kanban board
[...] ja kuten aina, taas tuli monta hyvää ideaa ja ajatusta. Mainitsemisen arvoinen on ainakin Samuli Heljon blogipostaus muutaman vuoden takaa. Artikkelissa kuvataan tarkasti erään taulun valmistuminen ja siihen [...]


Subscribe to RSS feed
The Tag Cloud
Agile Business Coaching Coding horror Conference Customer Design of Experiments Future Group dynamics ITIL It should not be that hard Java EE Kanban Leadership Lean Liferay Methodologies Natural UI Performance tuning Process Productivity Quality Retrospective RIA Scrum Six Sigma Social psychology Software Software architecture Testing This is great TOGAF
WP Cumulus Flash tag cloud by Roy Tanck and Luke Morton requires Flash Player 9 or better.
Samuli's Links
The Blog Archive
January 2013 (1)
February 2012 (1)
January 2012 (1)
November 2011 (1)
June 2011 (2)
May 2011 (1)
April 2011 (2)
March 2011 (2)
February 2011 (1)
January 2011 (1)
December 2010 (1)
November 2010 (1)
October 2010 (3)
September 2010 (3)
August 2010 (5)
July 2010 (2)
June 2010 (3)
May 2010 (4)
April 2010 (2)
March 2010 (6)
February 2010 (7)
January 2010 (3)
December 2009 (7)
November 2009 (6)







[...] team model When story is selected into development lane in our Kanban board, it is splitted into tasks like in sprint planning. During story analysis or while story is in [...]