In his keynote, David J. Anderson talks about what we've learned in 10 years of Kanban and shares a vision for the future direction enabling Enterprise Services Planning.
Sandy Mamoli explains how Trade Me is using Portfolio Kanban to reduce WIP by prioritizing projects, focusing on the important ones rather than urgent ones.
Martin L. Harbolt focuses on methods of providing data to a team to help them remain focused and maintain the rhythm necessary for success: KanBan boards, burn down charts and others, with examples.
Giovanni Asproni suggests that teams should not blindly embrace a methodology but rather create their own suiting their specific needs by using an approach based on patterns and pattern languages.
Allan Kelly introduces Xanpan, a mixture of Kanban, XP, Lean and economics, focusing on teams not projects, allowing for planned and unplanned work within iterations and levels flow.
Steve Arnold introduces Flow, an Agile method combining concepts from DevOps, Lean and Kanban, based on the idea that a requirement is worked on at each point of the software delivery pipeline.
Sandy Mamoli explains how to avoid multi-tasking by using personal Kanban and other Agile practices applied at the individual level.
Trevor Lalish-Menagh shares his experience introducing Kanban, what has worked and what hasn’t.
Gerry Kirk on how to be more effective using two Personal Kanban rules: Visualize Work and Start Stopping, Start Finishing.
Roman Pichler shares insight on Agile practices that can improve innovation, discussing the innovation stages and how product ownership, process, and project setup are influenced by uncertainty.
Jim Benson develops the idea that software is not engineered, and it is better done collaboratively by a communicative team using Agile and Kanban methodology and tools.