三津石智巳

👦🏻👦🏻👧🏻 Father of 3 | 🗺️ Service Reliability Engineering Manager at Rakuten Travel | 📚 Avid Reader | 👍 Wagashi | 👍 Caffe Latte | 👍 Owarai

【感想】Team Topologies

長いこと積読になっていたが読む。

It is increasingly clear that relying on a single, static organisational structure, like the org chart or matrix management, is untenable for effective outcomes with modern software systems.

p. 8

Simon Brown氏が言うところのdiagrams vs.modelsの話なのではと思った。org chartというひとつのviewでは全てを表現できないというだけの話なのでは。

結局のところ「Team Topologies」とは何かがいまいちハッキリしないのだが、Agile/Leanみたいな組織論におけるなにがしかの体系を示す固有名詞くらいに捉えるのが良さそう。

  • チームパターン
  • チーム間コミュニケーションパターン

かな。

  • Stream-aligned team: aligned to a flow of work from (usually) a segment of the business domain
  • Enabling team: helps a Stream-aligned team to overcome obstacles. Also detects missing capabilities.
  • Complicated Subsystem team: where significant mathematics/calculation/technical expertise is needed.
  • Platform team: a grouping of other team types that provide a compelling internal product to accelerate delivery by Stream-aligned teams

https://teamtopologies.com/key-concepts

  • Collaboration: working together for a defined period of time to discover new things (APIs, practices, technologies, etc.)
  • X-as-a-Service: one team provides and one team consumes something “as a Service”
  • Facilitation: one team helps and mentors another team
https://teamtopologies.com/key-concepts

話は変わるが、コングロマリット企業はその出自からして自然に各事業単位ではmicroservice architectureを取るのではと思う。各事業内をさらにmicroserviceに分割するのは不自然かもしれない。

When we change the organization structure to accommodate Coway's law, we are aiming to improve the space (context, constraints, etc.) in which organizations search for solutions with software systems.

p. 28

アルゴリズムの空間計算量の話みたいで面白い。どちらかというと、時間計算量のnを減らすみたいな話の方が分かりやすい。