If you have not been looking at how David Anderson is utilizing a Kanban system at Corbis, read his articles on it here.  The paper A Kanban System for Sustaining Engineering explains how they have implemented a pull system that utilizes lean and agile principles to assist in application mainatainence mode.  Davids group at Corbis also uses this in full blown project development.
I am planning on implementing this as a pull system for one our internal projects that I am in charge of.  The initial development we did using Agile XP methods to run the project.  That phase of the project used Iterations, daily stand-ups, automated builds, user stories, automated customer testing and more.  Now that we've deployed to production, the question is how do we handle left over user stories, and any change issues uncovered in the system testing?
I have been toying with implementing this type of system in some fashion and this seems the perfect opportunity.  Our change issues can be capped, so we can concentrate on this batch.  It would be interesting to see if this system could be utilized to handle all standard change requests (that don't require a major project).  I'll try to keep folks posted on how this works over the life of this experiment.
Happy PMing/Coding!
Share this post: email it! | bookmark it! | digg it! | reddit! | kick it! | live it!