Architecture for Flow with Wardley Mapping, DDD, and Team Topologies
summary
Combines Wardley Mapping, Domain‑Driven Design and Team Topologies to move an online‑school legacy system from a messy monolith into purpose‑aligned teams and cloud services: teams form a platform team to run a cloud migration (replacing on‑prem infra with cloud utilities and cutting operational effort), stream‑aligned teams refactor the monolith into bounded contexts using event‑storming, and dynamic re‑teaming enforces cognitive‑load limits so change flow speeds up and delivery bottlenecks shrink. Wardley Mapping guides what to build, buy or outsource and where to invest.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:03Local optimization fails
- 3:13Wardley Mapping DDD Team Topologies
- 5:40Wardley Mapping fundamentals
- 15:34Team Topologies for flow
- 19:30Architecting for flow
- 20:56Domain-Driven Design and subdomains
- 26:16Bounded contexts
- 29:08Team cognitive load
- 31:16Platform teams
- 33:03Efficiency gaps
- 34:07Team-first cloud migration
- 36:57Legacy to bounded contexts
- 39:44Team interactions
- 41:51Summary
- 42:12Q&A Wardley Mapping
- 42:56Q&A team balance
related talks
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
41mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
44mArchitecture for Flow - Wardley Mapping, DDD, and Team Topologies
43mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
56mOptimizing for a fast flow of value with adaptive, socio-technical systems
43mAdaptive Socio-Technical Systems with Architecture for Flow
40mAdaptive Socio-Technical Systems with Architecture for Flow
46mAdaptive Socio-Technical Systems with Architecture for Flow