Alan Claypool discusses a methodology meant to bring coherence to an organization based on a strategic vision and clear focus on core values, over-communication and up-down accountability.
Jim McCarthy discusses culture hacking, a distinct kind of culture engineering, expressing a particular hacker ethos, an ethos originating in the world of software hacking, promoting freedom, openness, and embodying rationality and design elegance.
Jeff Patton presents the process of co-creating products, where everyone is involved and responsible, taking examples from three companies he’s worked with.
Adrian Cho discusses applying Jazz performance principles to software development: managing friction, the importance of awareness, diversity, health, and leading on demand, embrace change and conflict.
Joanna Zweig and César Idrovo discuss Discovery Curves - a model to chart a team’s ability to learn-, and a group improvement process using past experiences and identifying common characteristics.
Luke Hohmann keynotes on what creates, causes, enables, and promotes software innovation.
Naveed Khawaja and Carl Bruiners introduce various Agile principles and practices and conduct a hands-on practice session meant to explain how to build a performing team.
Steve Rogalsky introduces the science of brainstorming and the practice of silent brainstorming which keeps loud people from dominating the meeting and helping quite people to contribute.
Dave Logan discusses why only 7% of organizational tribes are successfully doing Agile and what can be done about it.
Susan Standiford discusses the social psychology, culture and team dynamics challenges faced while moving RueLaLa to a new platform.
Jim Benson develops the idea that software is not engineered, and it is better done collaboratively by a communicative team using Agile and Kanban methodology and tools.
Sue McKinney discusses the roles of managers and developers within an organization where everyone owns delivery and is accountable.