If you're a busy CTO, the audiobook is just as excellent as the written one.
Team Topologies highlights the problems your org chart is creating for your software's architecture (and as a result, your business).
To remedy these problems, Matthew Skelton and Manuel Pais offer a different perspective on org structure in the form of four fundamental team topologies: value stream aligned teams, enabling teams, platform teams, and complicated subsystem teams.
The theory behind these team structures is chiefly built upon the premise of the Inverse Conway Maneuver, which "recommends evolving your team and organizational structure to promote your desired architecture." Ideally, this would require skilled software architects also be the architects of the teams in order to - for example - develop well-defined team APIs since software architects are already expected to be masters of API development.
Additionally, the concepts of developing sensing organizations, using Domain Driven Design to identify fracture planes, and managing a team's cognitive load are dissected to explain how to effectively structure high-performing teams.
If you have read and implemented the practices espoused in Project to Product, the Devops Handbook, and Accelerate but are still encountering communication bottlenecks and problems with scaling your existing team structures to meet product demands, then I highly recommend Team Topologies.
5.0 out of 5 starsTeam architecture for effective software architectures
December 3, 2019 - Published on Amazon.com
Format: PaperbackVerified Purchase
These guys really did their homework on reviewing the current literature, and building the case between team structure and the architecture of software. What I really liked is how the different operating and engagement modes for teams and between teams can evolve to affect healthy patterns for the software.
As a technology person it's easy for me to wrap my head around the patterns for teams just like the patterns for software, and how use can use one to influence the other for good (and bad) outcomes.
I bought both the Audio book and the physical book. They go great together, as you can listen to the audio version and then back it up with references to and re-reading the physical version.
Was reading intently until they mentioned they'd purposely restricted their engineers to only have one screen, so they could "look at each other more". I can't imagine how someone could decide to deliberately damage their engineer's productivity like that and get away with it. But perhaps they didn't, hence writing books now instead. Stuff like that is a real canary as to the wisdom of the authors of this book. Save your money.
It was everything I hoped it would be. This book gives very practical, easy to understand guidance on how to structure teams (especially technology teams) to incorporate the best of Agile,DevOps,etc. with minimal use of buzzwords. Highly recommend this book for anyone struggling to find the right team structure for fast flow.
5.0 out of 5 starsStream Align your teams with Team Topologies
January 9, 2020 - Published on Amazon.com
Team Topologies provides deep insight into organizing Development teams for high performance. It demonstrates why a team centric approach is critical to achieve your DevOps and Digital transformation goals.
For anyone leading team(s) or simply working in a team, you’re bound to learn a lot through the case studies and synthetic approach presented. You will acquire a new frame of reference to help evolve your team(s) or organization and improve Teamwork !
Optimize the alignment of your development team(s) and architecture(s) to your Business needs with Team Topologies. ( Full review "Stream Align Me" on LinkedIn )