Kiro Harada attempts to clear up some misconceptions on several Lean practices: Value Stream and Flow, Visualization, Pull-System, 5 Times Whys, Kanban, Kaizen.
Karl Scotland introduces the Kanban Canvas as a tool for applying Kanban Thinking in a hands-on session with participants learning how the different parts can help enabling continuous improvement.
Matt Philip discusses how to deepen the understanding of Kanban with depth-of-kanban assessments and through a series of experiments, emergence of a new role — the flow manager — and standard work.
Patrick Steyaert discusses how (traditional) Delivery and Discovery Kanban are similar but different along with several examples of Discovery Kanban systems based on dual strategies.
Andy Carmichael shares some lessons learned implementing a number of Kanban practices that have been subjected to an improving process.
In his keynote presented at the Lean Kanban UK 2014 conference, Mike Burrows offers helpful structure on how to organise your work so that your takeaways will be actionable.
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.