Margarette Purvis shares Food Bank’s kaizen journey of rethinking and improving operations by implementing small incremental improvements across the organization.
Emily Page and Doug Talbot discuss building trust in an organization by collecting feedback.
Ryan McKergow discusses how others have implemented scaled retrospectives, what worked and what didn’t work for his company, sharing tips on how to run scaled retrospectives and avoid wasting time.
Chris Young, who runs a live software system, discusses using Kanban metrics and practices with tools like Graphite and Grafana, and shows how the feedback helps businesses to make informed decisions.
Dan North discusses a number of feedback models and techniques, where and how to apply them, explaining the sandwich feedback model, how it works and why it usually doesn’t.
Matt Wynne and Steve Tooke talk about challenges in dealing with a distributed team and remote collaboration, the tools and practices that helped them, and how they approached continuous improvement.
Adam Krieger discusses improving CD: using feedback to improve customer satisfaction, treating DevOps as a responsibility, discovering the mindset and toolset necessary to deliver successfully.
Doug Talbot explains the importance of measuring to the Lean feedback cycle providing advice on what to measure and how often.
Ben Linders talks about the why and how of Agile retrospectives, with many practical tips, stories, and examples.
Scott Shaw, James Gregory describe the benefits of a polyglot approach to building enterprise software, showing how diversity can shorten feedback cycles and expose hidden business model assumptions.
Diana Larsen advises on how to get the most from retrospective practices, introducing a framework for getting better outcomes from retrospective meetings.
Ben Linders explains the "what" and "why" of retrospectives and the business value and benefits that they can bring.