A different take on (context) mapping -
summary
Argues that traditional context maps lack an anchor and a movement axis and shows a practical recipe: combine Wardley maps (evolution axis + position) with event storming and the bounded context canvas to visualize forces, anticipate change and pick refactor targets. Demonstrations include a day‑long map of a ticketing landscape that immediately exposes two misplaced bounded contexts and a custom time‑tracking piece to push to commodity (cloud) — a concrete, actionable outcome that works in practice.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:17Context maps
- 3:05Making context maps
- 6:52Predicting change
- 10:01Event storming
- 11:41Documenting
- 13:22The map
- 17:31Example of a map
- 26:44Core domain
- 35:01Design process
- 38:47QA
related talks
50mX Marks the Spot: Navigating Possible Futures with Wardley Maps
55mCharting the uncharted: Discovering and evolving bounded contexts
44mArchitecture for Flow - Wardley Mapping, DDD, and Team Topologies
39mFrom Domain Boundaries to Software Architecture
58mFrom here to there and back again
45mSystems Thinking by combining Team Topologies with Context Maps
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
47mBounded Contexts: Team Topologies and Architecture boundaries aligned