Lynne Cazaly explains how to apply visual maps, models, metaphors, templates and processes that help build buy-in, boost contributions and collaboration, and make communication a breeze within teams.
Martin Fowler keynotes on the importance of building a healthy social environment where software development can thrive. Part 1 of this presentation: www.infoq.com/presentations/workflow-refactoring
Ben Ross considers that physical environments affects agile practices, exemplifying with MYOB’s transformation of a shopping center’s roof into the largest open space in Melbourne.
Pete Cohen introduces the Business Model Canvas, a shared visual language for describing and designing business models, helping teams to achieve their goals within the context of an overall vision.
Josh Knowles shares thoughts on the strong engineering culture which has made the Pivotal Labs team successful, taking a look at how things have evolved over the past 20 years.
Matt Ballantine shares the approaches that have helped him to successfully deliver change in organizations by focusing on emotional reactions, stages of learning, old vs. new, peers influence.
Lisette Sutherland, Elinor Slomba share stories of successful remote distributed teams, how they built relationships and trust, and how they raised the quality of their communication.
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.
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 for real communication.
Martin Thompson focuses on the evolution of Java in contrast with C/C++, covering the cultural challenges of performance limits and how to collaborate with industry experts and organize teams.
Dan North believes Agile scales if teams achieve contextual consistency through shared guiding principles, a clear vision and a common understanding.