Architecting Independent Value Streams
summary
Argues that architecture must align business domains, teams and software into independent value streams and gives concrete techniques: use Domain‑Driven Design and event storming to find boundaries, apply Team Topologies and the Independent Service Heuristics to test team and budget viability (example: a proposed platform lacked its own budget), and run CodeScene to measure coupling (one client shows ~60% of code touched only by contractors). Recommends designing for domain-aligned, outcome-oriented, team-empowered and software-decoupled value streams.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:04Salesforce turning point
- 3:30Tightly coupled monoliths
- 5:41Teams align with domains
- 7:47Independent value streams
- 9:32Domain alignment in streams
- 15:34Outcome orientation
- 21:32Empowering teams
- 26:03Decoupling dependencies
- 33:00Modern architects tools
- 34:47Aligning teams domains software
- 36:31Q&A
related talks
30mThe Case for Value Stream Architecture
56mDesign and execute your own engineering strategy
01h 01mSoftware Architecture, Team Topologies & Complexity Science
49mArchitecture is Designing Knowledge Flow
49mDomain-Driven Design & Team Topologies For Product-led Organizations
56mOptimizing for a fast flow of value with adaptive, socio-technical systems
43mAdaptive Socio-Technical Systems with Architecture for Flow
43mSoftware Architecture, Design Thinking & Knowledge Flow