Rethinking Enterprise Software
summary
Claims that combining Event Storming with Event Sourcing/CQRS, Kanban and Management 3.0 turns discovery into behavior-first design. Workshops use orange post-its on a long paper roll to map domain events, expose hotspots and architectural coupling, and force developers to ask business questions. Teams prototype models to code the same day—often reaching green tests by afternoon—revealing legacy risks, reducing cross-team waiting, and yielding bounded contexts and read models that match real decisions rather than guessed classes.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker background
- 3:57Problems with software estimation
- 10:36Learning as a core development process
- 15:30Challenges in decision-making
- 21:34Enterprise software needs rethinking
- 27:19Event storming for business process modeling
- 37:41Modeling decisions in enterprise software
- 43:05Exploring multiple solutions and conflicts
- 49:09Rapid prototyping and user validation
- 54:32Defining completion in user stories
- 57:03Conclusion and Q&A
related talks
47mESSENTIALS - Event Storming for fun and profit
31mHow EventStorming Transformed Our Domain Modeling Process
50mHow EventStorming Transformed Our Domain Modeling Process
14mSession 1: Event Storming
40mEventStorming Lessons Learned - tens of thousands of post-its later
49mFrom Days to Hours: How EventStorming Transformed Our Domain Modeling Process
55mEvent Storming - how to shorten the distance between IT and Business
46mEvent Modeling from Beginner to Expert