Agile architects: classical conductors or band member?
summary
Breuninger runs an architecture practice split into enterprise, domain, software and platform responsibilities so that the online shop, ERP and logistics systems integrate without global chaos; teams own implementation while a central group defines cross-cutting guidelines. The company ships an in‑house shop across six new European countries and keeps 13 stores coordinated, with dedicated platform architect for front-end, platform architect for infra and platform architect for data/ML ops. Claim: architects alternate between teams own software architecture and being conveners, use relationship and expertise power, and favor pragmatic abstractions over ivory‑tower mandates.
AI-written summary · about
chapters (8)
- 0:00Conductor styles in music and architecture
- 3:57Architects as conductors or band members
- 7:29Architectural roles by focus
- 13:25Comfort zones in architecture
- 18:17Power dynamics in architecture
- 21:07Team autonomy vs enterprise architecture
- 22:30Architects in teams
- 23:10Passion in architecture
related talks
30mAgile architects: classical conductors or band member?
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
43mArchitect(ure) as Enabler of Organization’s Flow of Change
44mWhen your boss decides to have an architecture team…
01h 00mAgile Architecture
51mWhy We Need Architects (and Architecture) on Agile Projects
14mthe growing role of software architects
01h 09mAgile Software Architecture