Big picture event storming session
The big picture session invites as many people with business knowledge into a room to define an abstract timeline of the business.
The session goal is to align across functional operations. Hold a big-picture event-storming session to explain an abstract timeline of our business. This workshop will be significant, with anywhere from a manager to 20–30 people in attendance. Some colleagues have even held more extensive sessions with up to 70 participants. With around 20 participants, we expect to have a variety of perspectives in the room, not technical or business-related.
Invite the right people, including all the business representatives, IT people, and UX people.
Two key terms must be understood to understand event storming: a domain event and a domain expert. Yet, domain events represent facts about the domain, which only change when the underlying business changes. Usually, these conversations happen, but they all occur with event storming. This way, you can sort out any conflicts or discontinuities in any part of the domain while everyone involved is present and engaged. If the developers don’t understand the domain, they can’t model it.
An Event-storming session can lead to clarity of the business processes that the system needs to support.
Since the timeline gets codified as part of a sequence of events, we end up with the single source of truth of what the system represents. From there, we can drive the structure of the system. Events are not a transport for data but a transport for meaning. What we are doing is communicating changes in a specific period.
The communication mechanism we use at the business level will also be reflected in the code.
