Chapter 1: Cognitive Load
* Summary: The human brain has limited cognitive capacity, which can be overloaded by multitasking and complex tasks.
* Real Example: A developer may struggle to focus on code review while simultaneously responding to emails and chat messages.
Chapter 2: Conway's Law
* Summary: The structure of a system reflects the structure of the organization that designed it.
* Real Example: A team with hierarchical reporting lines will likely create systems with similar hierarchies.
Chapter 3: Scope Overload
* Summary: A team's workload can become unmanageable when it exceeds its cognitive capacity.
* Real Example: A team responsible for both frontend and backend development may find it difficult to meet deadlines and maintain quality.
Chapter 4: Communication Overload
* Summary: Teams can become overwhelmed by the volume and complexity of communication, especially when using multiple channels.
* Real Example: A team with members using various email threads, chat groups, and video conferencing platforms may face challenges in keeping everyone informed.
Chapter 5: Social Overload
* Summary: Team relationships can become strained due to social factors such as personality conflicts, individual motivations, and group dynamics.
* Real Example: A team with a highly competitive member may find it challenging to foster collaboration and trust.
Chapter 6: Cognitive Dissonance
* Summary: Teams may experience cognitive dissonance when their actions conflict with their beliefs or values.
* Real Example: A team that values autonomy but is subject to micromanagement may face distress and low morale.
Chapter 7: The Team Topologies Framework
* Summary: Introduces the Team Topologies framework, which provides guidance on team structure, communication, and cognitive load management.
* Real Example: A team can use the framework to transition from a "Solo" topology to a "Platform" topology, reducing cognitive load and improving communication.
Chapter 8: The Stream-Aligned Model
* Summary: Describes a team topology where work is divided into independently executable tasks that flow through a series of stages.
* Real Example: A DevOps team using a continuous delivery pipeline is an example of a Stream-Aligned team.
Chapter 9: The Feature Team Model
* Summary: Presents a topology where a team is responsible for the development and maintenance of a specific set of features.
* Real Example: A product team in charge of developing and supporting a particular module or component within a software application.
Chapter 10: The Enabling Team Model
* Summary: Explains a topology where a team provides supporting services, such as infrastructure, testing, or development tools, to other teams.
* Real Example: A cloud engineering team that manages and optimizes infrastructure for other development teams.
