Team Topologies: Organising Business and Technology Teams for Fast Flow is a compelling and insightful book by Matthew Skelton and Manuel Pais. Published in 2019, it has quickly become a go-to guide for organisations seeking to optimise their team structures for better software delivery. The book introduces a fresh perspective on how teams should be organised, focusing on the principles of flow and the importance of clear team boundaries.
At its core, Team Topologies argues that how teams are structured profoundly impacts their efficiency and effectiveness. Skelton and Pais propose that traditional organisational charts are often ill-suited for modern software development, where speed and adaptability are key. Instead, they advocate for dynamic team structures that can evolve alongside the needs of the business and the demands of the software systems being developed.
The book introduces four fundamental team types:
Stream-Aligned Teams: These teams are responsible for a specific flow of work, such as a particular product or service. They are designed to be as independent as possible, enabling them to deliver value without needing constant interaction with other teams.
Enabling Teams: These teams help other teams to become more effective, often by providing expertise or guidance in areas like DevOps, security, or testing. They are not directly involved in delivering features but play a crucial role in upskilling and supporting other teams.
Complicated Subsystem Teams: These teams handle areas of the system that require deep, specialised knowledge. They typically work on components that are critical to the overall system but are too complex for stream-aligned teams to manage directly.
Platform Teams: These teams provide internal services that other teams use, such as cloud infrastructure or developer tools. The aim is to create self-service platforms that reduce the cognitive load on stream-aligned teams, allowing them to focus on delivering features.
The authors also introduce three interaction modes between teams: collaboration, X-as-a-Service, and facilitating. These modes help define how teams should work together and ensure that interactions are productive and aligned with business goals.
Team Topologies is a must-read for anyone involved in software development or organisational design. The book is particularly relevant for those grappling with the complexities of scaling software delivery in large or rapidly growing organisations. Skelton and Pais offer a clear and actionable framework that can be tailored to different organisational contexts, making the book both practical and versatile.
One of the book’s strengths is its focus on flow and reducing cognitive load. By emphasising the importance of limiting the number of dependencies and handoffs between teams, the authors provide a pathway to faster, more reliable software delivery. The concept of “cognitive load” is particularly valuable, highlighting the often-overlooked impact of mental overhead on team productivity.
However, the book does have its limitations. While the authors provide numerous examples and case studies, some readers may find that the framework is more applicable to large enterprises than to smaller organisations or start-ups. Additionally, the book’s focus on software development might limit its appeal to those in other industries, although the principles could be adapted more broadly.
In conclusion, Team Topologies offers a fresh and thought-provoking approach to team design in the modern world of software delivery. Its emphasis on flow, clear team boundaries, and reducing cognitive load makes it a vital resource for any organisation seeking to improve its software delivery process. While it may not be a one-size-fits-all solution, it provides a robust framework that can be adapted to a wide range of organisational needs.