Architecture and Agility: A Shared Skillset!
summary
Claims that software architecture is effectively an implementation of agility, backed by concrete practices: use of architecture decision records to record iterated decisions, splitting macro vs micro architecture to assign responsibilities, and enabling team autonomy via Docker containers and Kubernetes. Gives a cautionary case: an expensive prototype for a module-by-module migration is cancelled when domain constraints surface. Argues engineers must iterate, document tradeoffs, and accept the illusion-of-control risk rather than freeze decisions.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 1:59Agility vs architecture stability
- 9:26Future-proof architecture bias
- 11:33Engineering is iterative
- 13:43Traditional architect role critique
- 20:25Architecture and agile teams
- 21:51Micro vs macro architecture
- 25:56Illusion of control in projects
- 31:14Key takeaways summary
- 32:16Q&A session
related talks
01h 09mAgile Software Architecture
38mAgile Architecture
01h 03mAgile Software Architecture
24mThe too many faces of Architecture
39mAgility in Software Architecture
36mAgile Software Development meets Business Agility
53mAgile and Architecture: a meeting of the undead
35mAgility and Architecture - Do Opposites Attract?