Book Notes: Team Topologies: Organizing Business and Technology Teams for Fast Flow
Overview
This post contains my notes on the book Team Topologies: Organizing Business and Technology Teams for Fast Flow by Matthew Skelton, Manuel Pais, and Ruth Malan.
You can find the book on Amazon
I’ll be adding my notes to this post as I read through the book. The notes will be organized by chapter and will include key concepts, code examples, and any additional insights I find useful.
Chapter 1: The problem with org charts
Overview:
- Conway’s law: Software architecture and team structure are similar forces
- Team Topologies
- clarifies team purpose and responsibilities
- Humanistic approach to building software systems
There are 4 fundamental team types:
- Stream-aligned team
- Enabling team
- Complicated subsystem team
- Platform team
Team structures must match the desired software architecture.
Cognitive Load: The total amount of mental effort being used in the working memory.
When cognitive load exceeds a team’s capacity, it leads to burnout and reduced productivity.
Obstacles to fast flow:
- blockers
- disengaged teams
- pushing against conways law
- software too big for teams
- confusing org design
- team pulled in too many directions
- Painful re-orgs
