Featured Whitepapers
- Apples, Oranges, and Acorns - All Agile Development Tools Are Not the Same
- One's Enough for Agile Application Development Management
- Requirements Management 101 – 4 Basics Everyone Should Know
- Tips on Requirements Traceability – Learn How to Control Change and Improve Quality
- Scaling Continuous Integration to Large and Distributed Teams
Agile Blogs
The Kanban board
Posted by: amehrabian@portofinosolutions.com
in Subscriptions |
Comment (0)
This is the third part of the Lean-Kanban post based on a training class I recently attended by David Anderson (aka @agilemanager) and some additional reading on the same subject. I will admit that I now favor this method of collaboration far more than Scrum and one of those reasons is Kanban’s explicit limitation of work made visible and enforceable through the Kanban board.
In Part 1 I covered some of my takeaways from the training and basic tenets of Kanban. In Part 2 I focused entirely on the notion of process policies. In this post I want to discuss the Kanban board, one of the key artifacts of the Kanban software development process.
At first glance, a Kanban board looks just like a Task board used in most Scrum environments.
Agile Marketplace - Announcements and Special Offers
The Business Case for ALM Transformation
Are legacy systems holding your company back? Breakthrough these technical constraints with an open and scalable environment that meets your unique business need to transform. There is no reason to be locked into an obsolete platform. The output of a number of recent transitions from legacy systems, this is practical white paper shares lessons learned and illustrates how guidance and enablement can pave the way for change.
Download this Whitepaper