Business Value Over Architecture?
summary
Explains a pragmatic decision map: plot uncertainty (new tech) versus rate of change, then pick one of four architecture supports — chief architect or community of practice for low-change/low-uncertainty; a technical service team (runs sprints, owns a technical backlog, accepts requests from feature teams) for high-change/high-uncertainty; and a technical consulting team as a rotating pool for mentoring. Describes timeboxed spikes/proofs of concept, how service teams prioritize with feature teams, and how roles evolve as the product stabilizes.
AI-written summary · about
chapters (7)
- 0:00Intro
- 5:39Architecture
- 6:54Complexity
- 11:01Chief Architect
- 11:27Community of Practice
- 13:29Service
- 16:55Technical Consulting
related talks
43mThinking Architecturally
44mWhen your boss decides to have an architecture team…
49mCultivating Architecture
30mBlending Product Thinking with Architecture
01h 03mAgile Software Architecture
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
37mArchitecting for Tomorrow: A Pragmatic Perspective
27mManaging architecture