Unlock the Full Potential of Event Storming with Qlerify
What is Event Storming?
Event Storming brings business people and developers closer together. It is one of the most powerful collaboration techniques on the planet and results from Event Storming workshops usually far exceed the participants' expectations.
In this webinar we will cover
Why is Event Storming so powerful?
Event Storming is based on a simple and ingenious concept, Key Domain Event. A Key Domain Event is an event in a business process that is expressed in past tense, for example "order placed". The concept is easy to understand for everyone and thus facilitates a high degree of involvement from the business. The organisation's representatives are called "Domain Experts" and with Event Storming you invite these domain experts and system developers to workshops where you explore business processes (the domain) together in a very time-efficient way.
During an Event Storming workshop, you brainstorm together and try to identify Key Domain Events. These events are then added to a timeline. Once this basic flow has been mapped, information is collected about which actors and systems are involved in the business process. Then you can choose to go continue in several directions and Event Storming is incredibly flexible in such a way that you can adapt the methodology to what information is to be collected and who the participants are. You can, for example, go further and build on with business rules, identified problem areas, users interfaces, etc.
There are three levels of Event Storming: Big Picture, Process Modeling and Software Design. In Big Picture, you map a business as a whole and try to find the biggest problems or opportunities in the business. Process Modeling focuses on an individual business process and tries to describe it in detail from start to finish, including all the alternative flows. Software Design is used when you want to get started quickly with the development of the system and with the help of this variant we can easily and quickly find which components we should build and how we should delimit our various subsystems. From a Software Design session, you automatically get Bounded Contexts and Aggregates. Bounded Contexts and Aggregates are concepts used in DDD (Domain Driven Design) and are used for designing the internals of software systems.