How EventStorming Transformed Our Domain Modeling Process
summary
Claims that domain modeling compresses from days to hours using EventStorming and a strict workshop recipe: a long wall, standing participants, lots of sticky notes, a visible timer and a facilitator. Start with orange sticky notes for past‑tense domain events, order them into pivotal events and swimlanes, mark hotspots (red) then vote with blue notes; add actors, commands, policies and read models, find bounded contexts and aggregates. Real runs yield ~10 hotspots in 2.5 hours, produce APIs/events before code, and sometimes stop projects, saving implementation effort.
AI-written summary · about
chapters (7)
- 0:00Introduction to EventStorming
- 11:57What is EventStorming
- 14:31How to run EventStorming
- 27:36Explicit walk-through phase
- 33:40Process modeling session
- 37:56After EventStorming next steps
- 44:11Q&A and closing remarks
related talks
31mHow EventStorming Transformed Our Domain Modeling Process
49mFrom Days to Hours: How EventStorming Transformed Our Domain Modeling Process
47mESSENTIALS - Event Storming for fun and profit
01h 02mEvent Storming for domain-driven design
41mEfficient Domain-Driven Design: An Introduction to Event Storming
14mSession 1: Event Storming
40mEventStorming Lessons Learned - tens of thousands of post-its later
01h 02mRethinking Enterprise Software