Team as code
summary
This presentation addresses how to expand DevOps/agile culture across an entire company by aligning software architecture with team structure. It draws on Team Topologies and similar frameworks (mentioning SAFe) and offers practical, iterative methods to change team topologies and inter-team communication channels (tech↔non‑tech) to reduce friction and maximize value delivery.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:20Team Topologies
- 7:24Conway's law limits
- 10:51Reverse Conway's law
- 13:27User experience
- 16:06Autonomous teams
- 19:38Avoid collaboration overload
- 22:06Measure user impact
- 24:37Break silos with goals
- 26:47Document collaboration modes
- 28:54Explicitness in remote work
related talks
35mHow a Lean and Structured Team Topology amplifies an Organisation's Productivity
45mTowards Architecture Organization Topologies
43mResilience, Scalability, Performance – On the Architecture of Agile Product Teams
37mDevOps Topologies 10 years on: what have we learned about silos, collaboration...
45mTowards Architecture Organization Topologies for Sustainable Fast Flow of Change
46mTowards Sustainable Learning, Designing and Decision-making
35mOrganization: A Tool for Software Architects
44mInsights on How Team Topologies Drive Organizational Success
