EventStorming is about learning and sharing a common understanding of a business.
Practice ( preferably 150 min)
How do we know that a development team understands something in the same way the business does?
How can we see and model a system as it really is, with all its complexity and ambiguities?
How do we know that we are working to solve the right problem ?
Resources:
Book :
By Alberto Brandolini (the inventor of EventStorming)
https://leanpub.com/introducing_eventstorming
This is an invaluable resources.
Online Communities :
Slack : https://ddd-cqrs-es.herokuapp.com/ , #event-storming channel, semi public
Google+ :https://plus.google.com/u/0/communities/113258571348605620818 public
Github: List of other resources.
https://github.com/mariuszgil/awesome-eventstorming/blob/master/README.md
https://github.com/mariuszgil/awesome-eventstorming/blob/master/README.md
EventStorming, especially the Big Picture format, is about discovering, learning and sharing
this common understanding, complexity and problems.
EventStorming takes its roots in Domain Driven Design.
It is about learning the domain, as fast as possible, together with the business
Breaking the silos that exists in some companies between business and IT.
So that we, in IT , can describe the model in business terms instead of technical ones.
Using only an unlimited supply of stickies, pens and long paper rolls on walls.
We will use a real domain (HR in goverment), with all it's ambiguities and peculiarities.
We will go from no knowledge about the domain to a Big Picture model, to more details on some of the key
aspects.
At the end of the session, you should be able to run, or at least dare to try out, EventStorming in your own
daily work.
Anybody involved in software :
from users to decision makers, developers, product owners, architects, ...
Participants will be able to experiment with EventStorming in their own domain.
I will gain new insights on my domain ;-)
- Lots of Stickies
- Pens
- Roll of Papers
- an available Flipchart / whiteboard would be handy
- I will need walls to hang long paper rolls....
The group will be divided.
* In the first first round each team will discover the Big Picture and discover the domain from a high level point of view
* In the second round each team will be steered into a specific part of the domain.
* In the last round , the team will be shuffled, with one or two member remaining, they will play the role of domain expert.
The new members will experience Legacy.
(This is to experience different learning and knowledge sharing aspect of a Big picture EventStorming session)
There will be multiple rounds of EventStorming, during that time I will play the role of domain expert.
Between the rounds
* the team will be encouraged to make small retrospective so that groups will discover what kind of issues
can arise during an eventstorming
* some incremental theory & tips will be added.
00:00- 00:20 theory : About EventStorming , explanation of Domain at large
00:20- 00:40 Doing : First round eventstorming - Big Picture
00:40- 01:00 Discussion: what went well, what was difficult,
01:00- 01:20 Doing : Second round eventstorming - Big Picture
01:20- 01:40 Discussion: Big Picture, what for.
01:40- 02:00 Doing : Third round eventstorming - Big Picture + Team shuffling
02:00- 02:20 Wrapup/questions : insights, where to go from here ?
10 minutes over to take into account the unexpected
Each team, during the first 2 rounds will be steered into a specific part of the domain in order to allow the shuffle of the third round
Pictures, Pictures, pictures...
Pointers & links to available resources.
- Doing it at work, a lot.
- Various meetups where modelleling techniques are discussed & tried out