Phil Poole presents ITV’s software development processes, the use of Kanban to adapt to change, to communicate to senior stakeholders, and to provide visibility of the project state.
Kiro Harada attempts to clear up some misconceptions on several Lean practices: Value Stream and Flow, Visualization, Pull-System, 5 Times Whys, Kanban, Kaizen.
Dimitar Bakardzhiev discusses planning a fixed bid project by applying the Monte Carlo simulation using collected historical data about lead time per story.
Joseph Yao introduces Transformation Priority Premise (TPP) as a way to learn TDD.
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.
Peter Niederwieser discusses building a continuous delivery pipeline using Gradle and Jenkins.
Bas Vodde introduces Large-Scale Scrum (LeSS), a framework for scaling Scrum to medium to large projects while staying true to the original Scrum principles.
Sam Newman, Zhamak Dehghani make an introduction to microservice architectures, explaining why they are ideal for organizations that want to optimize for fast speed of change.
Jason Toy talks about the evolution and history of LinkedIn's release strategy.
Sangeeta Narayanan goes over how Netfix got to the current continuous delivery state, the lessons they learnt and the successes they enjoyed along the way.
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.