Shane Hastie presents examples of how the most innocent of question or suggestion can send teams into a spin, and suggests a number of techniques to help create an environment where real communication can happen, irrespective if your team is co-located or distributed.
Martin Thompson focuses on the evolution of Java and how it contrasts to C/C++, covering the cultural challenges of pushing the limits of performance and how to collaborate with industry experts and organize teams, which often stands at odds with the culture in many organisations.
Dan North believes Agile scales if teams achieve contextual consistency through shared guiding principles, a clear vision and a common understanding.
Daniel Schauenberg provides insights into how Etsy develops software and what tools and processes they utilize to help them achieve their goals.
Dave Farley introduces the ideas of Continuous Delivery as a practical everyday, holistic process, using some of the techniques and technologies from a real world project as an example.
Andy Piper describes some fundamentals of communicating reliably in an unreliable world and communication techniques used to build distributed data structures that can tolerate failures.
Emma Langman explores the usefulness of some of the Quality tools that have been around since the 50s for gathering requirements, tackling repeat problems, or innovating more efficiently as a team.
Sam Aaron explores the idea of using programming languages, especially functional ones, to share ideas with other people, to have conversations, to support artistic practices, etc.
Tim Lister describes his work as a colleague, as an apprentice, as a mentor, and as a mediator noting how team dynamics have changed over the years, and how they bring new challenges to tight collaboration.
Ellen Grove teaches improving personal development using the Lego Serious Play thinking, communicating and problem solving technique.
Dan North shares insight on how really high-performing teams work, the patterns and ideas being genuine experiences from practitioners. This is Agile in actuality. Agile is an attitude, not a rule book.
David Hussman combats the addiction to a specific process, discussing various topics such as product thinking, regression deficit, building teams and connecting programs to portfolios.