Software Architects and Autonomous Teams
summary
Claims that architects often reduce team autonomy and proposes four concrete patterns: ivory tower, architect-in-team, architecture-without-architect, and architect-as-a-service. Implements the last pattern via a community of practice that embeds an architect into a team for about 2 months (planning with at least two architects so teams aren’t blocked), uses architecture decision records and open whiteboard sessions, and reports this model in production to enable autonomy while keeping knowledge and decisions documented.
AI-written summary · about
chapters (4)
- 0:00Start
- 1:19Architects can have negative impacts on autonomy
- 6:58Functional vs. Cross-functional
- 12:23Architects as part of the team
related talks
44mWhen your boss decides to have an architecture team…
02mHigh-performance teams
46mTHE too MANY FACES OF ARCHITECTURE
46mHow does the architect know?
52mThat's Not in My Job Description
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
08msoftware architecture and agile development
43mArchitect(ure) as Enabler of Organization’s Flow of Change