Here's a nice example of applying Kanban to a software development process, from David J. Anderson's “Agile Management Blog.” Has anyone used a process like this for managing open factory maintenance issues instead of software bugs?
Visit his blog for the details on how it works, but Anderson writes about the benefits of the “kanban” system:
The kanban system allows us to deliver on 3 elements of my recipe for success: reduce work-in-progress (in fact it limits it completely); balance capacity against demand (as new CRs can only be introduced when a kanban card frees up after a release); and prioritize.
Related in topic only, here's a webcast on Lean and Agile Software Management.
What do you think? Please scroll down (or click) to post a comment. Or please share the post with your thoughts on LinkedIn – and follow me or connect with me there.
Did you like this post? Make sure you don't miss a post or podcast — Subscribe to get notified about posts via email daily or weekly.
Check out my latest book, The Mistakes That Make Us: Cultivating a Culture of Learning and Innovation:
