InfoQ Article: Lean Kanban Boards for Agile Tracking
Agile projects are not the only ones to use “big visible charts” - Lean manufacturing, for example has its Kanban Boards. In Japanese "Kanban" means, loosely translated, 'card or sign'. In a Lean production system, each Kanban card is "pulled" into the system only when the work represented by an "in progress" card is retired. In this InfoQ article, Visualizing Agile Projects using Kanban Boards, Kenji Hiranabe explore visualizations currently used in Agile, then proposes using Kanban Boards to organize three viewpoints (Time, Task, and Team) to track project status and enhance collaboration.
The visualization tools he talks about are:
- Kanban Boards. Use a card as a token (Kanban) of a task, story, feature and stick them to a timeline (board). There are several levels of granularities, in three main combinations:
- Iteration-Story and
- Burndown Charts. Count the number of Kanbans (backlog tasks) and track it in a timebox to show the trend of work accomplished. There are also several levels of granularities.
- Parking lot Charts. Summarize the top-level project status.
- Calendars. There are a lot of variations of using calendars to show project status or plan.
In the article, Hiranebe introduces a uniquely Japanese addition to status tracking: the Niko-Niko Calendar, on which team members track their mood from day to day.
Hiranabe also mentions his software tool “TRICHORD” that implements Kanban Boards to realize project visualization from the three viewpoints.
Kenji Hiranabe is a frequent blogger and has translated a number of English Agile and XP books into the Japanese language.
Read the InfoQ article: Visualizing Agile Projects using Kanban Boards by Kenji Hiranabe.
Tracking relative to budgeted/available hours
Kanban Yahoo Group
I liked the paper you gave me to read. I wanted to make a comment about the parking lot diagram. It was first introduced on the original FDD project in Singapore and was first documented in Peter Coad's 1999 book, UML Modeling in Color in Chapter 6, the chapter written by Jeff De Luca.
And he started up a new Yahoo Group about Kanban Boards.
Re: Kanban Yahoo Group
TRICHORD has been released English Available Version.
We have released English Available Version on Sep.11,2007.
If you are interested in TRICHORD,Please visit our Site.
Re: TRICHORD has been released English Available Version.
Kanban should be real，touchable
Re: Kanban should be real，touchable
a board based on a sharepoint blog
Re: Kanban Yahoo Group
Online Kanban Tools
Works well when you have distributed teams, need history records, conversations recorded, etc.
Here comes all Kanban tools list....
Parking Lot Charts, WIP and Parking Lot Charts
It is interesting to note the hierarchy of feature and user story. FDD has always used a three-level feature-list hierarchy of feature or subject areas containing sets of features for each activity containing features. In FDD features are defined at a level of granularity close to that of a typical user story IME. Features are broken down into tasks during iterations but task progress itself is not reported in any formal way; feature milestones are tracked instead ... but then FDD was designed from the beginning for a larger project and team than the typical Scum/XP 7+/-2 project teams. See also borland.typepad.com/agile_transformation/2009/0...
One important concept for a Kanban board is work-in-progress limits. IMHO, it is this that makes it a true Kanban board. Otherwise, the board is little more, and probably less informative, than the old FDD feature milestone chart.
Stephen R. Palmer
Yoni Goldberg Oct 30, 2014
Dmytro Svarytsevych Oct 30, 2014