Architecture for Flow with Wardley Mapping, DDD, and Team Topologies
summary
Combines Wardley mapping to classify components (core/supporting/generic) with DDD bounded contexts—content creation, course/study, class management, learning support, plus evaluation, notifications and identity—and Team Topologies to reorganize teams. A platform team forms first to re-platform on-prem infrastructure to cloud, then three stream-aligned teams refactor the monolith into four core bounded contexts while one team owns supporting/generic concerns. Heuristics for cognitive load (teams own more commodity-right components) guide ownership, producing modular ownership boundaries and faster flow of change.
AI-written summary · about
chapters (16)
- 0:00The problem with local optimization
- 1:29Building the right thing right
- 2:34A holistic approach
- 3:20Legacy system challenges
- 5:30Introduction to Wardley Mapping
- 9:17Evolution of components
- 12:23Doctrine and principles
- 14:11Optimizing for flow with teams
- 15:38Team topologies explained
- 19:36Architecting for flow
- 21:02Domain-driven design
- 24:21DDD and mapping integration
- 28:43Structuring for team load
- 31:19Platform and team design
- 33:33Evolution and migration plan
- 39:16Summary and Q&A
related talks
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
45mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
44mArchitecture for Flow - 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
43mAdaptive Socio-Technical Systems with Architecture for Flow
45mAdaptive Socio-Technical Systems
46mAdaptive Socio-Technical Systems with Architecture for Flow