I (João Rosa) recently created an online cohort-based course, Effectively Manage Team Cognitive Load. Since the release of Team Topologies book, I have adopted its language and principles in my consultancy practice, supporting organizations in their digital transformation journey. I’ve noticed in the field that more people are aware of the effects of unmanaged Team Cognitive Load in their teams and organizations, using the concept presented in the Team Topologies book to drive changes in their organizations.

With the help of the wider community the Team Topologies team shapes library is now available in many common diagramming tools including Miro, Lucid Chart, Figma, Diagrams.net, Google Draw, Google Slides and PowerPoint.

We spoke to Darren Murph - Head of Remote at GitLab - about the opportunities and challenges presented by remote working for organizations building software-based systems and services. We were keen to get his insights into team-centric approaches to remote work.

Matthew Skelton und Manuel Pais haben mit ihrem Buch “Team Topologies” eine ausgezeichnete Beschreibung der Herausforderungen moderner Enterprise IT vorgelegt und bieten ein Modell an, das in vielen Fällen als Vorlage für eine effiziente Organisation herangezogen werden kann.

Robert Ruzitschka erklaert.

During the DevOps Enterprise Summit 2019 in Las Vegas, the authors of the “Team Topologies: Organizing Business and Technology Teams for Fast Flow” book - Matthew Skelton and Manuel Pais were interviewed by SolutionIQ’s Stas Zvinyatskovsky for the Agile Amped Podcast.

We spoke to Mark Phillips - author of Reinventing Communications - to discover insights into modern organizational dynamics from the viewpoint of project management and program management.

We spoke to Henny Portman to discover insights into modern organizational dynamics from the viewpoint of project management, programme management, and portfolio management.

Emily Webber is the author of the book Building Successful Communities of Practice and recently did extensive research (with anthropologist Professor Robin Dunbar) into the size and engagement dynamics of various communities of practice with a particular focus on how the group dynamics change as the group size crosses certain thresholds. The research was published in the academic publication PLOS ONE.

We spoke to Emily about her research and what the implications are for designing and evolving organizations.

Deployment pipelines can really help Stream-aligned teams to deliver software changes independently:

1. Deployment pipelines can help to reinforce an independent flow of change for a Stream-aligned team. Don’t forget to enable rapid feedback via telemetry!

2. Define the endpoints external to the team - these represent the “outside world” from team perspective. These external endpoints should be outside or at the domain boundary.

3. There can be huge value in managing your deployment pipeline “as a Service or as a proper product, with product management approaches.

We spoke to Andy Nesling - Product Manager for IoT Cloud at Dyson - about his recent experiences with using agile software delivery approaches to span teams in mobile, cloud, and embedded software systems.

We recently talked with Scott Prugh, Chief Architect & SVP Software Engineering at CSG, about some of the patterns and anti-patterns in the DevOps Topologies online catalog (predecessor of the Team Topologies book). We explore how the topologies have helped shape team structures and interactions at CSG.

I recently joined Mike Kavis of Deloitte on his OnCloud podcast to talk about team communication for effective software delivery. We covered the original DevOps Topologies patterns and how these have been used in industry, and then talked about what’s in the book Team Topologies: well-defined team types, what we mean by a modern platform, team interaction modes, clear responsibility boundaries, DevEx, and using difficulties in team interactions as ‘signals’ to the organization that something is missing or misplaced. We also talked about moving beyond the Spotify model - success in software delivery is not just about team structures but about how teams interact and what kind of relationships they create, sustain, and evolve.