Steve Rogalsky conducts a workshop on using the design studio approach to achieve effective collaborative design.
James Ross discusses what concept maps are, how to construct one, what to do and what to avoid when creating one, and how to help a team build a shared mental model depicted in a concept map.
Anders Ivarsson discusses how teams are autonomous at Spotify, how they are organized in squads, chapters, tribes and guilds, and how management and leadership works in their company.
Richard Kasperowski introduces the Core Protocols useful for intentionally building a great team culture, and demonstrates how to implement 3 of them.
Ben Gracewood explains how to grow a SaaS Product Engineering Team from 8 to 80 (and beyond) while driving simplicity by actively shedding rules and regulations.
Rhiannon Gaskell, Brett Wakeman, Rikki-Lee Vrankovich discuss how a hackathon sparked the change at Carsales AUS, followed by a number of initiatives that brought organizational agility.
Kevin Goldsmith presents Spotify’s internal culture promoting collaboration and creativity and the internal groupings that keep individuals and teams aligned and cross-functional.
John Housego describes how W. L. Gore & Associates manages to maintain a global corporation without hierarchies, that keeps the bureaucracy as small as possible.
Aaron Quint shares an honest story of a team's journey, taken from his experience as CTO of Paperless Post, an organization which went from 5 to over 100 people and from a dev team of 2 to 40.
Shane Hastie discusses the need for business analysis and requirements management, and showing how product ownership requires a team with a variety of skills and backgrounds to be effective.
Lisa Long talks about working with teams ranging from two people in an art gallery to three thousand spread across twelve time zones.
Randy Shoup discusses several important aspects of engineering cultures: hiring and retention, ownership and collaboration, quality and discipline, and learning and experimentation.