Event Storming

Events are baked into a domain, and communication between them occurs naturally. They are sent and consumed by different subdomains, and these interactions are translated into software in the future. We must understand the events to understand how a domain operates. There are some techniques that people can use to stay updated with the requirements, interactions, and restrictions that occur in a domain. Moreover, the scope of every requirement, interaction, and restriction is capped in a clear way for business and technical experts.

Why do we require a scoping session?

It is not an easy task to extract information from domain experts to write requirements for a system. Domain experts might explain business processes in one way, and technical experts might interpret them differently. This may lead to the construction of technical models —maybe in UML— which domain experts might not understand. Thus, there should be a session where both sides share their knowledge in the same terms. This will cause the requirements to appear naturally and for both sides, business and technical, to produce the domain model easily.

What is event storming?

Event storming is a collaborative workshop, created in 2012 by Alberto Brandolini, which allows technical and domain experts to create and share their knowledge of complex business domains and processes. It was widely adopted by the technology industry, and that is why it is one of the best ways through which technical teams can acquire knowledge about business processes from domain experts. Moreover, it is entertaining and easy to use, because sticky notes and pens are used to present information regarding business processes.