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.
Craig Strong and Daryn Holmes discuss applying the Theory of Constraints to software development, providing simulations and experience-based evidence to support the technique.
Ellen Grove presents a model for conflict recognition and resolution using practical games that teams can use to help clarify differing viewpoints and seek resolution.
Astrid Claessen discusses retrospectives: the Derby and Larsen models, how gamestorming helps, and techniques explained through example by involving the audience.
Bryan Beecham teaches the TDD principles with LEGO bricks, making technical concepts easier to grasp by working with your own hands.
Gojko Adžić explains how to ask questions and how to see things in a different perspective in order to get more from the software development process.
Ángel Medinilla outlines the basic steps he recommends to make for product success: product vision, business model, test assumptions, iterative and incremental development, use metrics, and keep it simple.
Hans Dockter discusses build systems from a declarative vs. imperative perspective, the importance of a rich execution model and problems with POM, providing examples from Gradle, Maven and Ant.
Sandy Mamoli explains how to avoid multi-tasking by using personal Kanban and other Agile practices applied at the individual level.
Rachel Laycock advises on designing systems for rapid deployment, avoiding delivering pitfalls by using micro services and evolutionary architecture.