Perhaps the greatest value of event storming is in the conversations it generates.

For the best outcomes, teams should combine event storming with implementation oriented toward domain-driven design. Instead, it results in a fully behavioral model that can be quickly implemented and validated. Besides being more enjoyable, event storming also results in more valuable insights as participants more readily engage in the process and offer their suggestions and expertise.Įffective: Event storming is not data modeling. It is a hands-on approach to domain modeling that invites each person to participate and interact. Straightforward: Rather than using complex UML, event storming breaks the process down into simple terms that both technical and non-technical stakeholders can understand.Įngaging: One of the goals of event storming is to make modeling fun. What used to take weeks can be accomplished in hours during a single workshop. By bringing key practitioners into the same room (literally or virtually), event storming has the advantage of being:įast: The event storming approach reduces the time it takes to create a comprehensive business domain model. Advantages of event stormingĮvent storming is designed to be both efficient and fun. Rather it is intended to support and accelerate the development process by bringing together relevant stakeholders to quickly model the broader business domain and its processes. Keep in mind, event storming is not a substitute for a UML diagram, design document, deployment plan, or other implementation models.

Originally created by Alberto Brandolini in 2012 as a quick alternative to precise UML diagramming, event storming is a workshop-style technique that brings project stakeholders together (both developers and non-technical users) to explore complex business domains. Event storming is a rapid group modeling approach to domain-driven design.

Lucidchart and whiteboard