The section of this talk that was about applying Kanban to an existing Scrum process, “Scrum-ban“, can be found on Corey’s blog. What this does for you is allows you to evolve Scrum into something that involves less ceremony (planning) around each sprint/iteration or how to move towards a leaner planning approach:
The ideal work planning process should always provide the development team with best thing to work on next, no more and no less.
The end result is a team that implements a pull model for new work. It asks for new work very frequently rather than batching it up each iteration. Batching leads to waste as more incomplete work is effectively added to the system. It does require some uniformity in the size of the work items entering the system for this approach to work however.
Corey’s article shows how to evolve a batched Scrum process into something that used pull so you don’t have to disrupt the team with a big change. I’d definitely like to see us do more of this at p&p.
Corey also has a list of the other Lean/Kanban related sessions at Agile 2008.