Team Topologies - yuuk1's Digital Garden

[Team Topologies](https://teamtopologies.com/) ## 紹介 DXが進み、ビジネスはIT・オンラインを基準に変化が加速している。この大きな流れを受けるのがソフトウェア開発である。またソフトウェア業界としては、アジャイルやDevOpsなどの手法を開発して、時代の移り変わりの速度に合わせるように、いかに効率的にサービスを提供できるかを試行錯誤してきた。本書は高速なデリバリーを実現することを目的とした、4つの基本的なチームタイプと3つのインタラクションパターンに基づく、組織設計とチームインタラクションのための実践的な適応モデルを紹介する。これは、ソフトウェアの組織設計における大きな前進であり、チームの相互作用と相互関係を明確に定義した方法を提示することで、チーム間の問題を組織の自己運営のための貴重なシグナルに変え、結果として得られるソフトウェアアーキテクチャをより明確で持続可能なものにする。これにより組織に適したチームパターンを選択して進化させ、ソフトウェアを健全な状態に保つことで、バリューストリームを最適化するのに役立たせることができるだろう。 [チームトポロジー - JMAM 日本能率協会マネジメントセンター「人・組織・経営の変化」を支援するJMAMの書籍](https://pub.jmam.co.jp/book/b593881.html) ## 目次 PART I デリバリーの手段としてのチーム Chapter1 組織図の問題 Chapter2 [[コンウェイの法則]]が重要な理由 Chapter3 チームファースト思考 PART Ⅱ フローを機能させるチームトポロジー Chapter4 静的なチームトポロジーチームのアンチパターン Chapter5 4つの基本的なチームタイプ Chapter6 チームファーストな境界を決める PART Ⅲ イノベーションと高速なデリバリーのためにチームインタラクションを進化させる Chapter7 チームインタラクションモード Chapter8 組織的センシングでチーム構造を進化させる Chapter9 まとめ:次世代デジタル運用モデル ## 関連資料 - [運用技術者組織の設計と運用 / Design and operation of operational engineer organization - Speaker Deck](https://speakerdeck.com/nari_ex/design-and-operation-of-operational-engineer-organization?slide=51) - [Team Topologiesを読んだ | Taichi Nakashima](https://deeeet.com/writing/2020/02/06/team-topologies/) - [チームトポロジーの読書した内容をまとめる](https://zenn.dev/hajimeni/scraps/aed34edc0246f3) - [【資料公開】30分で分かった気になるチームトポロジー | Ryuzee.com](https://www.ryuzee.com/contents/blog/14566) ## References 1. Conway, Melvin E. “How Do Committees Invent?” *Datamation*, April 1968, 28–31. 2. MacCormack, Alan, Carliss Baldwin, and John Rusnak. “Exploring the Structure of Complex Software Designs: An Empirical Study of Open Source and Proprietary Code.” *Harvard Business School*, August 2012. 3. Sosa, Manuel E., Sean D. Eppinger, and Daniel E. Whitney. “The Impacts of Platform Architecture on Product Development and Production.” In *Design Structure Matrix: A Tool for Managing Complex Technical and Social Systems*, edited by Ali A. Yassine, 419–38. London: CRC Press, 2004. 4. Malan, Ruth. “Conway’s Law.” *ruthmalan.com*, May 2, 2018, https:// ruthmalan.com/Posts/2018/2018-05-Conways-Law/. 5. Conway, Melvin E. “Toward Simplifying Application Development: A Dozen Lessons from Veterans.” In *Proceedings of the Extreme Programming and Agile Processes in Software Engineering*, edited by Helen Sharp and Peyman K. J. Hansson. Berlin: Springer, 2004. 6. Forsgren, Nicole, Jez Humble, and Gene Kim. *Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations*. Portland, OR: IT Revolution Press, 2018. 7. Nygard, Michael. *Release It! Design and Deploy Production-Ready Software*. Raleigh, NC: The Pragmatic Programmers, 2007. 8. MacCormack, Alan, John Rusnak, and Carliss Y. Baldwin. “The Influence of Architectural Evolution on the Costs of Software Maintenance.” *Harvard Business School Technology & Operations Management Unit Working Paper*, August 2006, 1–43. 9. Roberts, John. *The Modern Firm: Organizational Design for Performance and Growth*. Oxford: Oxford University Press, 2004. 10. Reinertsen, Donald G. *The Principles of Product Development Flow: Second Generation Lean Product Development*. Redondo Beach, CA: Celeritas Publishing, 2009. 11. Malan, Ruth. “Agility Requires Architecture, and Vice Versa.” *ruthmalan.com*, August 17, 2018, https://ruthmalan.com/Posts/2018/2018-08-Agility- Architecture/. 12. Kelly, Allan. “Software Architecture vs. Code.” *Twitter*, May 13, 2018, 5:51 a.m., https://twitter.com/allankellynet/status/995659670834917376. 13. Stanford, Naomi. *Guide to Organisation Design: Creating High-Performing and Adaptable Enterprises*. London: KoganPage, 2015. 14. Sosa, Manuel E., Sean D. Eppinger, and Daniel E. Whitney. “The Impacts of Platform Architecture on Product Development and Production.” In *Design Structure Matrix: A Tool for Managing Complex Technical and Social Systems*, edited by Ali A. Yassine, 419–38. London: CRC Press, 2004. 15. Cohn, Mike. *Succeeding with Agile: Software Development Using Scrum*. Boston: Addison-Wesley, 2010. 16. Kniberg, Henrik. “Spotify Engineering Culture (Part 1).” *labs.spotify.com*, October 14, 2014, https://labs.spotify.com/2014/03/27/spotify-engineering- culture-part-1/. 17. Driskell, James E., Eduardo Salas, and Jennifer L. Johnson. “Does Team Training Improve Team Performance? A Meta-Analytic Review.” *Human Factors: The Journal of the Human Factors and Ergonomics Society* 53, no. 6 (December 2011): 515–29. 18. DeMarco, Tom, and Timothy Lister. *Peopleware: Productive Projects and Teams*, 3rd ed. Boston: Addison-Wesley, 2011. 19. Stanford, Naomi. *Guide to Organisation Design: Creating High-Performing and Adaptable Enterprises*. London: KoganPage, 2015. 20. Deming, W. Edwards. *Out of the Crisis*. Cambridge, MA: MIT Press, 2000. 21. Reeves, Martin, Simon Levin, and Daichi Ueda. “The Biology of Corporate Survival: How to Navigate the Adaptive Valley.” *Harvard Business Review*, January 2016. 22. Sweller, John. “Cognitive Load During Problem Solving: Effects on Learning.” *Cognitive Science* 12 (1988): 257–85. 23. Pearce, Jo. “Cognitive Load in Software Development.” *Medium*, August 2, 2018, https://medium.com/ @jlpearce/cognitive-load-in-software-development- f4285403d261. 24. Driskell, James E., Eduardo Salas, and Jennifer L. Johnson. “Does Team Training Improve Team Performance? A Meta-Analytic Review.” *Human Factors: The Journal of the Human Factors and Ergonomics Society* 53, no. 6 (December 2011): 515–29. 25. Jay, Graylin, David Dig, John Richards, and Craig Anslow. “Runtime Cognitive Load Estimation and Optimization.” In *Proceedings of the 11th IEEE International Symposium on Wearable Computers*, 129–36. New York: IEEE, 2009. 26. McChrystal, General Stanley. *Team of Teams: New Rules of Engagement for a Complex World*. New York: Portfolio/Penguin, 2015. 27. Mohammed, Sabah, Pieter van den Heuvel, and Paul Van den Bosch. “Predicting Team Performance from Team Mental Models.” *Small Group Research* 43, no. 4 (August 2012): 364–92. 28. Helfand, Heidi. *Dynamic Reteaming: The Art and Wisdom of Changing Teams*. New York: Addison-Wesley Professional, 2017. 29. Cockcroft, Adrian. “Migrating to Microservices, Part 4: How to Reorganize Your Teams for Microservices.” *nginx.com*, July 21, 2015, https://www.nginx.com/blog/ migrating-to-microservices-part-4-how-to-reorganize-teams/. 30. Burgess, Mark. *In Search of Certainty: The Science of Our Information Infrastructure*. Sebastopol, CA: O’Reilly Media, 2015. 31. Kniberg, Henrik. “Spotify Engineering Culture (Part 1).” *labs.spotify.com*, October 14, 2014, https://labs.spotify.com/2014/03/27/spotify-engineering- culture-part-1/. 32. Kniberg, Henrik, and Anders Ivarsson. “Scaling Agile @ Spotify with Tribes, Squads, Guilds, and Chapters.” *labs.spotify.com*, November 11, 2012, https:// labs.spotify.com/2012/12/11/scaling-agile-at-spotify-with-tribes-squads-guilds- chapters/. 33. Doorley, Scott, and Scott Witthoft. *Make Space: How to Set the Stage for Creative Collaboration*. Hoboken, NJ: John Wiley & Sons, 2012. 34. Fried, Jason, and David Heinemeier Hansson. *Remote: Office Not Required*. London: Ebury Business, 2013. 35. Laloux, Frédéric. *Reinventing Organizations: A Guide to Creating Organizations Inspired by the Next Stage in Human Consciousness*. Brussels: Nelson Parker, 2014.