EventStorming Workshop

A quick introduction and some guidelines

Presentation agenda

  • The what and why of Event Storming
  • Guidelines to the event storming workshop
What and why 1/4

There are three common problems in organizations

  1. Evolution
  2. (Invisible) Misalignment
  3. Lack of holistic view
What and why 2/4

Big picture event storming is:

A chaotic and highly collaborative exploration of the whole, focusing on the behaviour

Also:

An inclusive and more objective way to have meaningful discussions and make decisions

What and why 3/4

Event Storming works

  • A shared, holistic view
  • Surfaces problems and inconsistencies, and helps solve them
  • Discover natural "seam lines"
  • And more...
What and why 4/4

Techy(?) bit: Systems are behaviour-driven

  • Processes
  • People
  • Value

Workshop guidelines

Workshop guidelines 1/8

This may be uncomfortable 😞 in the beginning but...

Workshop guidelines 2/8

...it becomes amazing quickly 😊

Workshop guidelines 3/8

Expectations from you

  • Actively contribute - get out of your comfort zone
  • No messaging, no calls, no emails (unless it's an emergency)
  • Focus
  • Relax during the frequent short breaks
Workshop guidelines 4/8

Things you should know

  • Add stickies, even if you're not sure
  • This is a safe environment
  • There are no wrong answers
Workshop guidelines 5/8

There are no wrong answers

  • The cost of missing information can be large
  • Mistakes are easy to fix
  • EventStorming is a very cost-efficient way to experiment
Workshop guidelines 6/8

At the end

  • We do not expect a clean model
  • We do expect:
    • A clean, end-to-end narrative
    • Clear picture of problems
    • A useful model

Months of development and frustration can save you a few hours of modeling

A few hours of modeling can save you months of development and frustration

You can find this presentation here: https://skleanthous.github.io/presentations/

Savvas Kleanthous on twitter:
Valadis Novakovits on twitter:

Evolution -> The software struggles to keep pace with the changing needs of the business. Moreover, there Misalignment -> between software and business processes. Lack of holistic view -> No-one has a holistic view of the business. Decisions are locally optimized. At worst locally optimized decisions can actively harm the organization

- Heuristics to align software with business process - Discussions finally happen Event storming brings people with the right questions together with the people that have the answers, and gives them a tool to discuss. Importantly they all Event storming makes discussions more objective Event storming is more inclusive because the visible model allows others to contribute By discovering conflicts and inconsistencies, and discussing and solving them, we can discover seam lines.