Don Reinertsen proposes addressing uncertainty not by considering it harmful nor by embracing it but by efficiently reducing it in the context of the economic laws governing the software dev process.
Jesper Boeg shares his experience, lessons learned, failures, and common problems met when introducing Kanban to various teams having no previous Agile or Lean experience
Dan North shares his experience in a new endeavor working for a trading company with distributed teams embracing ideas from Lean and Theory of Constraints.
Don Reinertsen outlines the need for using an economic model for development, explaining what that is emphasizing the cost of delay, how an economic model looks like, how to build and use one.
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?