Email	Print Reprint
	add to:
	Del.icio.us Digg Google Furl	Slashdot Y! MyWeb Blink
	TABLE OF CONTENTS Introduction Kanban Board as Primary Information TRICHORD

TRICHORD

We have been developing an agile project management tool called TRICHORD. "TRI" means the three viewpoints -- Time, Task, and Team -- and "CHORD" means harmony.

It works as a workplace to share project status in the whole team, providing the three levels of Kanban Boards -- Feature Kanban (Release-Feature), Story Kanban (Story-Iteration), and Task Kanban (Daily-Task) -- as described in Table 1. A Feature Kanban is supported by a Parking Lot Chart, Story, and Task Kanbans are supported by Burndown Charts.

In addition, TRICHORD has a Niko-Niko Calendar service to share the team mood. It also works as a simple "twitter"-like SNS communication center in the projects.

TRICHORD is implemented on Eclipse RCP (Rich Client Platform), and optionally works with Trac (issue tracking system).

6 Acknowledgements

Mary Poppendieck reviewed this paper thoroughly and provided lots of advice and suggestions, for which I am most thankful.

References

Akira Sakata, "Niko-niko calendar", 2006 (www.geocities.jp/nikonikocalendar/index_en.html).

Kent Beck, "Extreme Programming Explained 2nd ", 2005 Addison-Wesley "Informative workspace" is a practice of XP.

Alistair Cockburn, "Agile Software Development", 2001 Addison-Wesley The word "information radiator" is first used.

Alistair Cockburn, "Crystal Clear", 2004 Addison-Wesley "Burndown/up chart" is discussed as a powerful technique.

Mike Cohn, "Agile Estimating and Planning", 2005 Prentice Hall "Burndown chart" is most deeply discussed.

Ron Jeffries, "Big Visible Chart", 2004 (www.xprogramming.com/xpmag/BigVisibleCharts.htm).
Mary and Tom Poppendieck, "Lean Software Development", 2003 Addison-Wesley

Mary and Tom Poppendieck, "Implementing Lean Software Development", 2006 Addison-Wesley. Explains Kanban in TPS and how it works as a pull process mechanism.

Ken Schwaber, et al. "Agile Software Development with SCRUM", 2001 Prentice Hall

Jim Highsmith, "Agile Project Management", 2004 Addison-Wesley. Here, Feature Kanban is called Feature breakdown structure and feature planning on whiteboard.

Stephen R. Palmer et al., Practical Guide to Feature-Driven Development, 2002, Prentice Hall. First introduced Parking Lot Chart

Previous Page | 1 Introduction | 2 Kanban Board as Primary Information | 3 TRICHORD

RELATED ARTICLES Nozzle: Counteracting Memory Exploits Experts Consider Robots, Legal Issues ZigBee Alliance, DLMS User Assoc Collaborate on Metering Data Compatibility Cloud Computing: Detecting Scalability Problems Logging In C++ : Part 2		TOP 5 ARTICLES No Top Articles.