Published on 28 August 2013 by @mathiasverraes
Event Storming is a technique where you get the developers and the business stakeholders in a room, and visualize the business processes. You do this using stickies with domain events and causality (such as commands), and end with drawing boundaries for aggregates, bounded contexts and subdomains. It’s developed by Alberto Brandolini and is deeply rooted in Domain Driven Design, and CQRS/ES.
I facilitated an Event Storming session with the team of Qandidate.com in Rotterdam. I’ve read an early draft of Alberto’s paper on Event Storming, that inspired most of what I did. It was my first time doing this as a facilitator, so I’d thought I’d share my notes. It’s just the raw material – I was going to process them into something more readable first, but Jef Claes convinced me to just post them as is. So forgive me if they are vague; I promise I will blog about Event Storming more later.
Despite my rookie mistakes (too much intervention, then too little) the whole thing went very well. The team was very excited, they want to do it again with their founders. We also did a bit of context mapping for the legacy systems of their parent company, but time ran out.
I think there are three main reasons for Model Storming:
Follow @mathiasverraes on Twitter.
|Modelling Heuristics||Workshop @ Domain-Driven Design Europe||workshop||Amsterdam, NL||Feb 1|
|Conference||Domain-Driven Design Europe 2017||organiser||Amsterdam, NL||Jan 31 - Feb 3|
|Domain-Driven Design||Neos Conference||workshop||Hamburg, DE||Mar 30|
|Keynote (TBD)||Neos Conference||keynote||Hamburg, DE||Mar 31|
This work by Mathias Verraes is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 License.