Agile architects: classical conductors or band member?
summary
Breuninger runs a team aligned ecommerce org with 15 development teams (3–8 FTE each) and splits roles into enterprise, domain, platform and software architects so software architecture stays inside teams while platform architects set macro guidelines like loose coupling and front end standards. An architecture team of 5–6 people centralizes cross‑team decisions; current staffing is ~4 platform architects (data front infra backend), 1 architect per 2–3 teams for domain concerns and 1–2 full‑time enterprise architects, and this setup is working though it risks becoming an ivory tower.
AI-written summary · about
chapters (7)
- 0:00Introduction and orchestra analogy
- 3:42Architects as conductors
- 8:19Types of architects defined
- 14:36Leadership and power in architecture
- 20:36Architecture teams vs team ownership
- 24:50Finding your architectural style
- 25:55Q&A on team structure and ratios
related talks
25mAgile architects: classical conductors or band member?
44mWhen your boss decides to have an architecture team…
51mWhy We Need Architects (and Architecture) on Agile Projects
16mEveryone architect!
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
40mIs it possible for enterprise architects to be really agile?
14mthe growing role of software architects
01h 00mAgile Architecture