Pedro Canahuati discusses some of the ways the Production Engineering (PE) team at Facebook has worked on building a collaborative culture between the software and operations teams.
Paul Martin uncovers the hidden barriers to body-language skill development and shares a technique that improves the positive communication abilities of people.
Richard Weissel advises Agile organizations to spend some time understanding what it is that makes the classroom environment a classic example of collaborative working based on trust and respect.
Neha Batra believes that the best teams are the ones with diverse ways of working, diverse opinions, and diverse backgrounds, but with great diversity comes great responsibility.
Marina Cantacuzino presents lessons on reconciliation and forgiveness learned from real life cases, teaching how to overcome division, resolve tension and learn to embrace difference.
Eben Halford takes a look at what makes teams different from groups, the structures that enable teams, team motivation, intervention models and the role of social capital in facilitating teams.
Matt Wynne and Steve Tooke talk about challenges in dealing with a distributed team and remote collaboration, the tools and practices that helped them, and how they approached continuous improvement.
Jeremy Edberg discusses remote teams and the pitfalls they’ve run into, the parts that are working well, and a summary of their research talking to other fully or partially remote teams.
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.
Mike Breeze and Ma Qiang share the story of a distributed team and its Agile transformation, placing individuals and interactions over processes and tools and avoiding the dark side of Agile.
Hannah Mittelstaedt talks about how Etsy dissolved the traditional Android and iOS teams and trained tons of web developers in app development.
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.