Barry O'Reilly discusses how to embrace a culture of continuous experimentation and learning, to adapt the organization’s design, and transform the business to an adaptable, resilient Lean Enterprise.
Trevor Owens takes an in-depth look at the methodologies, tools, and incentive structures that are guiding some of the word's largest organizations to reclaim their innovation progress.
Sam McAfee focuses on quantitative risk modeling approaches exploring how to bring scientific rigor back into the Lean Startup process with Monte Carlo simulations and Cost of Delay scenarios.
Joakim Recht discusses how Tradeshift moved from manual deployment processes to automation and what this means in terms of organizational scalability, technology, transparency, and culture.
Glen Ford discusses how Zeebox applies and refines Lean: methods, experiments, discovery and feature teams, cultural challenges, innovation, etc.
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.
Barb Spurway, Tracy Bowman discuss Voice of the Customer (VoC), a Total Quality Management/ Lean Manufacturing concept helping teams build quality products from the customers’ perspective.
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.
Jason Little discusses how to avoid an organizational change failure when introducing Agile by leveraging principles of Lean Startup and Customer Development.
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.
Nick Zhu & Sharan Karanth introduce a thought framework, based on Anti-Fragility, that can be used to describe, explain, and tune Agile, Lean as well as Continuous Delivery practices.
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.