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.
If you’re working to build a culture where people feel safe to speak up, solve problems, and improve every day, I’d be glad to help. Let’s talk about how to strengthen Psychological Safety and Continuous Improvement in your organization.
