Team Topologies: Organizing Business and Technology Teams for Fast Flow

NOTES

Foreword

1.	Conway, “How Do Committees Invent?.”

Preface

1.	Skelton, “What Team Structure Is Right for DevOps to Flourish?”
2.	Skelton, “How Different Team Topologies Influence DevOps Culture.”

Chapter 1

1.	Schwartz et al., Thinking Environments, 21.
2.	Pflaeging, Organize for Complexity, 34–41.
3.	Pflaeging, Organize for Complexity.
4.	Laloux, Reinventing Organizations; Robertson, Holocracy.
5.	Stanford, Guide to Organisation Design, 14–16.
6.	Conway, “How do Committees Invent?, 31.
7.	Conway, “How do Committees Invent?”; Kelly, “Conway’s Law & Continuous Delivery.”
8.	Kelly, “Conway’s Law v. Software Architecture.”
9.	Raymond, The New Hacker’s Dictionary, 124.
10.	Lewis, “Microservices and the Inverse Conway.”
11.	Pink, Drive, 49.

Chapter 2

1.	“DevOps Over Coffee – Adidas;” Fernando Cornago, person email communication with the authors, March 2019.
2.	MacCormack et al., “Exploring the Structure of Complex Software Designs,” 1015–1030; MacCormack et al., “Exploring the Duality Between Product and Organizational Architectures,” 1309–1024.
3.	Sosa et al., “The Misalignment of Product Architecture and Organizational Structure in Complex Product Development,” 1674–1689.
4.	Malan, “Conway’s Law.”
5.	Conway, “How do Committees Invent?” 28.
6.	Forsgren et al., Accelerate, 63.
7.	Nygard, Release It!, 4.
8.	MacCormack et al., “Exploring the Structure of Complex Software Designs.”
9.	Roberts, The Modern Firm, 190.
10.	Reinertsen, The Principles of Product Development Flow, 257.
11.	Malan, “Conway’s Law.”
12.	Kelly, “Return to Conway’s Law.”
13.	Stanford, Guide to Organisation Design, 4.
14.	Sosa et al., “The Misalignment of Product Architecture.”
15.	Cohn, “Nine Questions to Assess Scrum Team Structure.”
16.	Kniberg, “Real-Life Agile Scaling.”

Chapter 3

1.	Driskell and Salas, “Collective Behavior and Team Performance,” 277–288.
2.	McChrystal et al., Team of Teams, 94.
3.	Rozovsky, “Re:Work—The Five Keys to a Successful Google Team.”
4.	Crawford, At opening quotes. “Amazon’s ‘Two-Pizza Teams.’”
5.	Dunbar, “Neocortex Size as a Constraint on Group Size in Primates,” 469–493.
6.	Snowden, “The Rule of 5, 15 & 150;” Dunbar, How Many Friends Does One Person Need?; Bennett, “The Dunbar Number, From the Guru of Social Networks;” Burgess, Thinking in Promises, 87.
7.	Snowden, “The Rule of 5, 15 & 150;” Karlgaard and Malone, Team Genius, 201–205.
8.	Lewis, “Microservices and the Inverse Conway Manoeuvre.”
9.	Munns, “Chris Munns, DevOps @ Amazon.”
10.	Brooks, The Mythical Man-Month.
11.	Tuckman, “Developmental Sequence in Small Groups,” 384–399.
12.	Kelly, Project Myopia, 72.
13.	Helfand, Dynamic Reteaming, 123.
14.	Knight, “Acquisition Community Team Dynamics.”
15.	Humble et al., Lean Enterprise, 37.
16.	Driskell and Salas, “Collective Behavior and Team Performance;” Rock and Grant, Why Diverse Teams Are Smarter.
17.	Jang, “Cultural Brokerage and Creative Performance in Multicultural Teams,” 993–1009; Carayon, “Human Factors of Complex Sociotechnical Systems,” 525–535.
18.	DeMarco and Lister, Peopleware, 156.
19.	Stanford, Guide to Organisation Design, 287.
20.	Deming, Out of the Crisis, 22.
21.	Roberts, The Modern Firm, 277.
22.	Sweller, “Cognitive Load During Problem Solving: Effects on Learning,” 257–285.
23.	Pearce, “Day 3: Managing Cognitive Load for Team Learning;” Pearce, “Hacking Your Head.”
24.	Driskell et al., “Does Stress Lead to a Loss of Team Perspective,” 300.
25.	Jay et al., “Cyclomatic Complexity and Lines of Code,” 137–143.
26.	MacChrystal et al., Team of Teams, 94.
27.	Lim and Klein, “Team Mental Models and Team Performance,” 403–418.
28.	Evan Wiley, as quoted in Helfand, Dynamic Reteaming, 121.
29.	Jeff Bezos, as quoted in Lane, “The Secret to Amazon’s Success.”
30.	Axelrod, Complexity of Cooperation; Burgess, Thinking in Promises, 73.
31.	Kniberg and Ivarsson, “Scaling Agile @ Spotify.”
32.	Kniberg and Ivarsson, “Scaling Agile @ Spotify.”
33.	Forsgren et al., Accelerate, 181.
34.	Jeremy Brown, personal communication with the authors, March 2019.
35.	Doorley and Witthoft, Make Space, 16.
36.	Fried and Hansson, Remote, 91.

Chapter 4

1.	Stanford, Guide to Organisation Design, 3.
2.	Kniberg and Ivarsson, “Scaling Agile @ Spotify.”
3.	Kniberg and Ivarsson, “Scaling Agile @ Spotify.”
4.	Kniberg and Ivarsson, “Scaling Agile @ Spotify.”
5.	Forsgren et al., Accelerate, 63.
6.	Skelton, “What Team Structure Is Right for DevOps to Flourish?”
7.	John, “DevOps for Service Providers—Next Generation Tools.”
8.	Hastie, “An Interview with Sam Guckenheimer on Microsoft’s Journey to Cloud Cadence.”
9.	Ben Treynor, as quoted in Niall Murphy, “What is ‘Site Reliability Engineering’?”
10.	Dogan, “The SRE Model.”
11.	Rensin, “Introducing Google Customer Reliability Engineering.”
12.	Netflix Technology Blog, “Full Cycle Developers at Netflix—Operate What You Build.”
13.	DeGrandis, Making Work Visible, 82.
14.	Strode and Huff, “A Taxonomy of Dependencies in Agile Software Development.”
15.	Pulak Agrawal, personal communication with the authors, March 2019.
16.	Pulak Agrawal, personal communication with the authors, March 2019.

Chapter 5

1.	Luo et al., “Transitioning from a Hierarchical Product Organization to an Open Platform Organization.”
2.	Reinertsen, The Principles of Product Development Flow, 265.
3.	Lane, “The Secret to Amazon’s Success—Internal APIs;” Hoff, “Amazon Architecture.”
4.	Crawford, “Amazon’s ‘Two-Pizza Teams;’” Munns, “Chris Munns, DevOps @ Amazon.”
5.	Kramer, “The Biggest Thing Amazon Got Right.”
6.	Sussna, Designing Delivery, 148.
7.	Pink, Drive, 49.
8.	Eckstein, “Architecture in Large Scale Agile Development,” 21–29.
9.	Robert Greenleaf, The Servant as Leader.
10.	DeMarco and Lister, Peopleware, 212.
11.	Webber, Building Successful Communities of Practice, 11.
12.	Bottcher, “What I Talk About When I Talk About Platforms.”
13.	Eckstein, Agile Development in the Large, 53.
14.	Neumark, “DevOps & Product Teams—Win or Fail?”
15.	Reinertsen, The Principles of Product Development Flow, 292.
16.	Womack and Jones, Lean Thinking.
17.	Urquhart, “IT Operations in a Cloudy World.”
18.	Kniberg, “Real-Life Agile Scaling.”
19.	Kelly, Business Patterns for Software Developers, 88–89.
20.	Conway, “Toward Simplifying Application Development, in a Dozen Lessons.”
21.	Shibata, “How to Build a Platform Team Now!”
22.	Shibata, “How to Build a Platform Team Now!”
23.	Beer, Brain of the Firm, 238.
24.	Shibata, “How to Build a Platform Team Now!”
25.	Hall, “ITSM, DevOps, and Why Three-Tier Support Should Be Replaced with Swarming.”
26.	Forsgren et al., Accelerate, 68.

Chapter 6

1.	Forsgren et al., Accelerate, 63.
2.	Forsgren et al., Accelerate, 66
3.	Bernstein and Turban, “The Impact of the ‘Open’ Workspace on Human Collaboration.”
4.	Evans, Domain-Driven Design.
5.	Fowler, “Bliki: BoundedContext.”
6.	Tune and Millett, Designing Autonomous Teams and Services, 38.
7.	Nygard, “The Perils of Semantic Coupling.”
8.	Helfand, Dynamic Reteaming, 203.
9.	Hering, DevOps for the Modern Enterprise, 45.
10.	Phillips, “Testing Observability.”

Chapter 7

1.	Bernstein et al., “How Intermittent Breaks in Interaction Improve Collective Intelligence,” 8734–8739.
2.	Rother, Toyota Kata, 236.
3.	Kim and Pierce, “Convergent Versus Divergent Thinking,” 245–250.
4.	Urquhart, “Communications and Conway’s Law.”
5.	Betz, Managing Digital, 253.
6.	Burgess, Thinking in Promises, 105.
7.	Reinertsen, The Principles of Product Development Flow, 233.
8.	Malan, “Conway’s Law.”
9.	Kelly, “Return to Conway’s Law.”
10.	Helfand, Dynamic Reteaming, 121; Wiley, as quoted in Helfand, Dynamic Reteaming, 121.
11.	Helfand, Dynamic Reteaming, 13.
12.	Reinertsen, The Principles of Product Development Flow, 254.

Chapter 8

1.	Forsgren et al., Accelerate, 63.
2.	Ingles, “Convergence to Kubernetes.”
3.	Ingles, “Convergence to Kubernetes,”
4.	Sussna, Designing Delivery, 61.
5.	Kotter, “Accelerate!”
6.	Drucker, The Daily Drucker, 291.
7.	Stanford, Guide to Organisation Design, 17.
8.	Narayan, Agile IT Organization Design, 65.
9.	Kim et al., The DevOps Handbook, 11.
10.	Sussna, Designing Delivery, 58.
11.	Narayan, Agile IT Organization Design, 31.

Conclusion

1.	Conway, “How do Committees Invent?” 31.
2.	Manns and Rising, Fearless Change.