Jim Benson notices that some organizations keep their silos and have even created a DevOps one, suggesting that what is needed is a UXDevQAOPS group or simply Collaborative Development.
Steve Rogalsky conducts a workshop on using the design studio approach to achieve effective collaborative design.
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.
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.
Randy Shoup discusses several important aspects of engineering cultures: hiring and retention, ownership and collaboration, quality and discipline, and learning and experimentation.
Adam Yuret discusses how a focus on resource efficiency impedes flow while creating mountains of failure demand and fracturing an organization into competing silos.
Mike Pearce tells the story of how MOO manages to keep a fresh, startup-like culture that fosters innovation and values collaboration, while still delivering products and looking after its staff.
Ward Cunningham discusses the designs goals of a federated wiki.
Jenni Jepsen shares the neuroscience behind why human brain is wired to connect with others, and how to use that to delight customers and stakeholders every day.
Matt Barcomb shares practical ideas for generating and validating projects as Real Options, using value models and risk consideration to create a framework for prioritization and decision-making.
Sallyann Freudenberg takes some very different slants on the psychology of programming and explores how each of them might be better supported: cognitive, autistic, introverted / extraverted.