Architecture for Flow with Wardley Mapping, DDD, and Team Topologies
summary
Combines Wardley mapping, Domain‑Driven Design and Team Topologies into a concrete plan: re‑platformed infrastructure to cloud‑hosted services to cut ops effort, decomposed a monolithic “big ball of mud” into bounded contexts aligned to subdomains, and formed stream‑aligned, platform, and enabling teams using dynamic re‑teaming and evolving interaction modes. Claims faster flow of change, lower team cognitive load, and stepwise refactoring supported by a thinnest viable platform and cloud migration (replatform then refactor).
AI-written summary · about
chapters (30)
- 0:00Introduction
- 1:09Building the Right Thing
- 2:09Adaptive Solution
- 3:12Team Topologies
- 4:48Wardley Mapping
- 9:17Climatic Patterns
- 10:16Evolution Stages
- 11:10Doctrine
- 12:22Online School
- 13:01Team Perspective
- 14:14Team Topologies Overview
- 16:23Collaboration
- 17:56Architecture for Flow
- 20:14Strategic Design
- 20:45Core subdomains
- 21:21Supporting subdomains
- 21:55Generic subdomains
- 22:41Online School Example
- 27:10Team Boundaries
- 28:01Characteristics of Evolution Stages
- 29:20Clear Responsibility Boundaries
- 29:48Services
- 30:44Team constellation
- 31:17Efficiency gaps
- 33:09Infrastructure components
- 33:38Cloud migration journey
- 34:26Replatforming
- 35:10Cloud Migration
- 36:12Refactoring
- 37:27Cloud Journey
related talks
44mArchitecture for Flow - Wardley Mapping, DDD, and Team Topologies
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
45mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
56mOptimizing for a fast flow of value with adaptive, socio-technical systems
40mAdaptive Socio-Technical Systems with Architecture for Flow
43mAdaptive Socio-Technical Systems with Architecture for Flow
43mAdaptive Socio-Technical Systems with Architecture for Flow
46mAdaptive Socio-Technical Systems with Architecture for Flow