In Team Topologies IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions for IT through four fundamental team topologies and three interaction modes.

Figures & Tables Case Studies & Industry Examples Foreword by Ruth Malan Preface PART I TEAMS AS THE MEANS OF DELIVERY Chapter 1: The Problem with Org Charts Communication Structures of an OrganizationTeam Topologies: A New Way of Thinking about TeamsThe Revival of Conway's LawCognitive Load and BottlenecksSummary: Rethink Team Structures, Purpose, and Interactions Chapter 2: Conway's Law and Why It Matters Understanding and Using Conway's LawThe Reverse Conway ManeuverSoftware Architectures that Encourage Team-Scoped FlowOrganization Design Requires Technical ExpertiseRestrict Unnecessary CommunicationBeware: Naive Uses of Conway's LawSummary: Conway's Law Is Critical for Efficient Team Design in Tech Chapter 3: Team-First Thinking Use Small, Long-Lived Teams as the StandardGood Boundaries Minimize Cognitive LoadDesign "Team APIs" and Facilitate Team InteractionsWarning: Engineering Practices Are FoundationalSummary: Limit Teams' Cognitive Load and Facilitate Team Interactions to Go Faster PART II TEAM TOPOLOGIES THAT WORK FOR FLOW Chapter 4: Static Team Topologies Team Anti-PatternsDesign for Flow of ChangeDevOps and the DevOps TopologiesSuccessful Team PatternsConsiderations When Choosing a TopologyUse DevOps Topologies to Evolve the OrganizationSummary: Adopt and Evolve Team Topologies that Match Your Current Context Chapter 5: The Four Fundamental Team Topologies Stream-Aligned TeamsEnabling TeamsComplicated-Subsystem TeamsPlatform TeamsAvoid Team Silos in the Flow of ChangeA Good Platform Is "Just Big Enough"Convert Common Team Types to the Fundamental Team TopologiesSummary: Use Loosely Coupled, Modular Groups of Four Specific Team Types Chapter 6: Choose Team-First Boundaries A Team-First Approach to Software Responsibilities and BoundariesHidden Monoliths and CouplingSoftware Boundaries or "Fracture Planes"Real-World Example: ManufacturingSummary: Choose Software Boundaries to Match Team Cognitive Load PART III EVOLVING TEAM INTERACTIONS FOR INNOVATION AND RAPID DELIVERY Chapter 7: Team Interaction Modes Well-Defined Interactions Are Key to Effective TeamsThe Three Essential Team Interaction ModesTeam Behaviors for Each Interaction ModeChoosing Suitable Team Interaction ModesChoosing Basic Team OrganizationChoose Team Interaction Modes to Reduce Uncertainty and Enhance FlowSummary: Three Well-Defined Team Interaction Modes Chapter 8: Evolve Team Structures with Organizational Sensing How Much Collaboration Is Right for Each Team Interaction?Accelerate Learning and Adoption of New PracticesConstant Evolution of Team TopologiesCombining Teams Topologies for Greater EffectivenessTriggers for Evolution of Team TopologiesSelf Steer Design and DevelopmentSummary: Evolving Team Topologies Conclusion: The Next-Generation Digital Operating Model Four Team Types and Three Interaction ModesTeam-First Thinking: Cognitive Load, Team API, Team-Sized ArchitectureStrategic Application of Conway's LawEvolve Organization Design for Adaptability and SensingTeam Topologies Alone Are Not Sufficient for IT EffectivenessNext Steps: How to Get Started with Team Topologies Glossary Recommended Reading References Notes Index Acknowledgments About the Authors