EventStorming is a workshop-based method to quickly find out what is happening in the domain of a software program.[1] Comparing to other methods it is extremely lightweight and requires intentionally no support by a computer. The result is expressed in sticky notes on a wide wall. The business process is "stormed out" as a series of domain events which are denoted as orange stickies (Wikipedia definition)

My first contact with EventStorming was accidental, it was just a new method proposed by someone from the team for fast introduction into the domain. Nowadays, after few years of practicing, using it in different projects, providing workshops and digging into EventStorming (as Alberto said many times, we just only scratched the surface!) this technique became one of my most important tools.

Do you need to know this tool? No matter if you work on green-field software, legacy application or even non-IT project, you will find benefits in this technique. So... why not?

It's developer's (mis)understanding, not expert knowledge that gets released into production

• Alberto Brandolini

You can find here some links to interesting materials, articles or presentations about EventStorming. Pull-requests are always welcome!

EventStorming offers notation for process and software modeling, like Events, Commands, Aggregates, Read Models... Notation is open and you can always add your own elements to make model even better. This is why I'm using Rules, Metrics, Alerts and few other concepts. It's always about embedding different perspectives into model, making them visible.

2x3h of Big Picture sessions we performed in our project:

• Introducing EventStorming, Alberto Brandolini
• Domain-Driven Design Distilled, Chapter 7: Acceleration and Management Tools, Vaughn Vernon

• Introducing EventStorming, Alberto Brandolini
• Facilitating EventStorming, Mathias Verraes
• An introduction to EventStorming: The easy way to achieve domain-driven design, Steven A. Lowe
• Modelling Reactive Systems with EventStorming and Domain-Driven Design, Kevin Webber
• EventStorming: On Fake Domains and Happy Paths, Mathias Verraes
• EventStorming, Storytelling, Visualisations, Mathias Verraes
• EventStorming Exercise, Tim Schraepen
• EventStorming: Warsztaty Product Craftsmanship Agile Wrocław, Rafał Makara (PL)
• How to Use Event Storming for Product Development, Andrzej Samek
• Event Storming and Spring with a Splash of DDD, Jakub Pilimon
• EventStorming's Coincidence with Business Process Improvement

• 50.000 Orange Stickies Later, Alberto Brandolini
• EventStorming, Paul Rayner
• Event Storming for fun and profit, Dan North

• EventStorming Recipes, Alberto Brandolini
• Model Storming, Alberto Brandolini
• EventStorming, Colaborative Learning for Complex Domains, Paul Rayner

• Alberto Brandolini, inventor of EventStorming
• Mathias Verraes
• Dan North
• Mariusz Gil
• Alexey Zimarev
• Adam Dymitruk
• Marco Heimeshoff
• Martin Schimak
• Nick Tune

I'm sorry if I missed someone related to the topic...

Have you ever been at "remote" party or tried to listen few parallel discussions the same time? Ok, you know the answer...

• DDD by Example, Factory

• EventStormers Google+ Community
• DDD/CQRS/ES Slack see the #event-storming channel

There are some interesting articles not directly connected to main topic, but underlaying concepts.

• How to spot a liar: get them to tell their story backwards
• Detection of Deception: Cognitive Load
• Divergent, Emergent & Convergent Thinking, Performance People Pty Ltd