How To Ruin An Event Storming With Two Little Techie Mistakes
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away. ― Antoine de Saint-Exupéry, Airman’s Odyssey
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away. ― Antoine de Saint-Exupéry, Airman’s Odyssey
In this part, we went deep into the technical details. Let’s take a step back from Design Level Event Storming!
Stuck in repetitive workflow issues? Learn to spot and fix vicious cycles with this practical guide.
Let’s take a Big Picture of the Big Picture Event Storming! Here is a summary of everything we wrote about this Event Storming, plus references to go deeper.
How to use Event Storming with legacy systems? Forget the legacy: think system's evolution.
You modeled your workflow with Event Storming. Now use a metaphor to give a name to this model. This post explains how and why this is good practice.
Use Design-Level Event Storming to identify Aggregates, UX mockups, and other design elements. Just follow this agenda through your first facilitation!
Design Level Event Storming relies on advanced Domain Driven Design vocabulary. Here is how to make things simple for your participants.