Benjamin Mitchell advices on carrying team conversations about information presented on Kanban boards helping members to change their thinking and acts in order to achieve evolutionary change.
Stuart Charlton presents Canadian Pacific’s strategy for a modern IT: adopting hybrid cloud, introducing Agile/Lean development, automating everything, distributed data systems, RESTful integration.
Jesper Boeg discusses why it is important to deliver software early, why it is difficult to do so, along with tools/tips/practices: shared vision, story maps, coaching, and others.
Joshua Kerievsky discusses Lean Startup -a disciplined, scientific and capital efficient method for discovering and building products and services that people love-, comparing it with Agile.
Rick Simmons presents a launch process meant to introduce a team to Kanban in two days, focusing on the core concepts and techniques, and by setting the team on an improvement path.
James Sutton presents why Kanban works well in software development and how it can improve the culture of a group using it. Sutton also touches complementary Lean ideas and tools.
Jez Humble discusses innovating using a Lean startup approach and overcoming innovation barriers in enterprises along with engineering practices useful for rapid delivery of quality software.
Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?
Joel Semeniuk shares some of the lessons he learned managing development teams, how he got into Kanban and why its principles are helpful.
In this presentation Don Reinertsen examines some key lean methods including queue management, batch size reduction, WIP constraints, and cadence. He also discusses the governing economic tradeoffs and how these methods can be exploited by product developers.
David J. Anderson explains how to use predictability, measurement and change management to balance the factors of observed capability, staffing, and delivery targets to achieve predictable outcomes.
Benjamin Mitchell believes that Kanban risks to become a fad if it does not cover gaps related to experiencing embarrassment and threat, proposing a solution based on the double-loop learning model.