Matthew McCullough examines the last four years of communication culture at GitHub, starting their internal mobile and web apps, use of pull requests, and emoji.
Glen Ford discusses how Zeebox applies and refines Lean: methods, experiments, discovery and feature teams, cultural challenges, innovation, etc.
Angela Harms keynotes on the importance of improving relationship and communication through empathetic listening, authentic connection and compassion rather than applying practices blindly.
Bill Liao keynotes on the scale-free self-organizing systems implemented by CoderDojo and how they can be used by other consumer software organizations that wants to achieve significant reach.
Karen Siers outlines the difficulties encountered by a developer switching from a waterfall or cowboy coding environment to a collaborative Agile style.
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.