Organization: A Tool for Software Architects
summary
The talk explains how to deliberately use organizational structure and team practices as a tool for software architecture, referencing Conway’s Law, domain-driven design, microservices, and DevOps/Accelerate research. It shows concrete actions architects can take—beyond technical design—such as shaping team boundaries, running workshops, offering support and training, and fostering culture to enable collaborative architecture without undermining team autonomy.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:51Architects do architecture & tech
- 7:44Organization must be defined
- 15:19Accelerate: The science of lean software & DevOps
- 18:51Software architecture = Collaborative games
- 21:14Architects shouldn't do architecture
- 22:12Start: more than trainings
- 25:22Support
- 26:20Workshop
- 28:35Culture issues
- 33:29Conclusion
related talks
45mTowards Architecture Organization Topologies
31mHow and Why to Design Your Teams for Modern Software Systems
18mBuilding Platforms, Breaking Code How Your Org Chart Can Support or Wreck Progress
01mConway's Law
45mConway's Law: when best practices aren't enough
41mSoftware architecture as a contributor to high performing teams
46mArchitecture for Cross-Functional Teams
41mArchitecture and Organization