Event Modeling
summary
Event Modeling describes systems as a timeline of factual events and a storyboard of UX and projections, paired with Event Sourcing so every state change is replayable. Teams switch to fixed‑price slices, remove 90% of meetings, stop using issue trackers for seven years, and eliminate code reviews; production bugs consistently take under four hours to fix. A Fortune 50 trading rewrite succeeds after two intense days of event modeling, proving the blueprint cuts rework and speeds delivery.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:50The History of Information Systems
- 3:29Blueprints
- 5:10Event Modeling
- 6:30Memes
- 8:18Alignment
- 9:05Feedback
- 9:53Planning Meetings
- 10:08Change Management
- 10:25Issue Trackers
- 11:13Death March
- 11:56Scope
- 14:13Test
- 14:40BDD
- 15:38Specifications
- 16:28Information completeness
- 21:30DomainDriven Design
- 23:05EventDriven Architecture
- 26:06No Estimate Movement
- 26:45Change Infrastructure Anytime
- 27:22Slices
- 28:24No Code Reviews
- 30:16No Imposter Syndrome
- 33:26Event Sourcing
- 34:15MVP
- 34:47Login
- 35:30History
- 39:43Tools
- 40:31Questions
related talks
55mFrom Days to Hours: How EventStorming Transformed Our Domain Modeling Process
33mEvent Storming for Everyone
54mThinking in Events
43mEvent driven development
49mFrom Days to Hours: How EventStorming Transformed Our Domain Modeling Process
38mEvery Event, Everywhere, All at Once
01mLightning talk about Event Modelling
21mEvent is the new Model