ℹ️ NOTE: An updated version of this post has been published on the Event Storming Journal blog
This is the 7th post in a series about how to use Event Storming to kick start architecture on good tracks. If you want to learn how I got into Event Storming, I recommend you to start reading from the beginning.
This is also the 3rd part of a post detailing the agenda for a Domain Driven Design Big Picture Event Storming. Please make sure to read the previous articles first.
If you went through the previous steps, all the attendees should have a good grasp of the domain. Let’s test this understanding a bit.
Now is the time to check that the whole picture makes sense. Since the beginning of humanity, stories have been the vehicle of knowledge. Knowledge used to go from generation to generation through campfire stories. Our brains are hard-wired to listen, remember and make sense of stories.
Ask for a volunteer from the audience, or for a few if people are afraid to do it alone. Then ask the first volunteer to narrate the story of the system. He just needs to go through the events chronologically and explain what happens.
As the narrator speaks, the audience will raise questions and notice incoherences. This is again a time to add, remove or replace events to fix the story. A few extra definitions might emerge. If a problem seems too big to fix during the session, park it with a pink problem post-it.
Narrating the story can be pretty tiring, so ask a new narrator to take over at some point.
8. Reverse storytelling
For an even greater drill down in the domain, reverse storytelling is the way to go. Get a few more volunteers and ask them to tell the story from the end. Naming this step ‘storytelling’ is not accurate. It’s rather repeatedly asking “What might have triggered this event?”. This will generate or update events, actors or external systems.
The reason this works so well is that questions trigger the creative parts of our brains. We get to imagine all kinds of new possibilities. This phase is very productive and brings a lot of insights.
This is it, you’ve reach the end of the DDD Big Picture Event Storming. At this point, it’s a good idea to settle down and assess the outcomes.
💡 By far the biggest outcome of DDD Big Picture Event Storming is a better shared understanding of the domain.
You might actually be wondering what the deliverables are. At this point, most deliverables are intangibles :
- By far the biggest is a better shared understanding of the domain. This will save tremendous time by improving collaboration. It will avoid specification bugs, and enable a better design.
- All together, you have identified problems. Fixing these problems might be quick wins with high payoff.
- The definitions are the first bricks of an Ubiquitous Language. Leveraging on it saves on-boarding time and maintains the system’s conceptual integrity.
- Finally, this was also a mandatory step for collaborative architecture. A good shared understanding of the domain makes discussions about functional architecture possible.
Thus, the next steps can be:
- To fix a major problem. In his book, Alberto Brandolini recalls such a situation. The Big Boss actually had every other work stopped until they fixed a ‘new’ problem.
- To continue to grow the ubiquitous language, by adding and refining definitions
- To do more workshop in order to draft a target architecture. I’ll explain how to do this in the next posts.
Depending on your session, the next steps might be more or less obvious. If they are not, it’s a good time to have an open discussion to get everyone’s opinion. Once the next steps are clear and taken care of by someone, call it a day and end the workshop.
Don’t forget to ask for feedback on the session itself before people leave. A ROTI is a quick way to do this.
The series continues
💡 Event Storming unlocks drafting an architecture, drawing teams and a sustainable refactoring path.
That’s it, after a few hours, you’ve reached the end of DDD Big Picture Event Storming. This is the massive knowledge-sharing foundation step. It will help us to draft an architecture, draw teams, find a sustainable refactoring path and more. In the next post I will give a few personal tips about running a DDD Event Storming.
This was the 7th post in a series about how to use Event Storming to kick start architecture on good tracks.