Knowledge crunching is one of the most important aspects of Domain-Driven Design (DDD). EventStorming offers one of the most effective and fun method to get domain knowledge from people that will be using the system you are building. Check this presentation to know more about this awesome modelling technique, which is formulated by Alberto Brandolini.

1. Introduction
to Event Storming
#eventstorming
@zimareff

2. Ideal flow
This is how it should work, right?

3. The reality
Not so nice, no, no, no :(

4. Domain-Driven Design
Knowledge crunching
Talking to domain experts
Figuring out the language
Linking problem space to solution space

6. Effectiveness

7. Alberto Brandolini
@ziobrando

8. EventStorming
People with questions
Meeting people with answers
In one room
Plus…

9. Modelling Space

10. Unlimited

11. Notation

12. Simple

13. Enough stationary

14. Domain Events
Represent facts
State transition
Past tense
Anyone can do it

15. First one is hard
Do it yourself

16. Let them go
There are no mistakes

17. Observe the rules
But don’t play boss

18. Big Picture
People with questions
People with answers
In one room
Unlimited modelling space
Lots os stationary

19. Prepare the space
Remove chairs
Remove tables
At least try
Bring fruits and drinks

20. Be time keeper
Time box the whole thing
Plan breaks
Cut too detailed discussions

21. Mark hotspots

22. Hotspot signs
Not enough clarity
Puzzled faces
Heated discussions
Gently burn the fire, put a pink sticky

23. Do it now

24. Design Level
Extended notation
Commands
Users
Read models

25. One picture
That explains it all
Image credit: Alberto Brandolini

26. Start small
Increment

27. There is something
in between your stickies

28. Whiteboard
That compiles

29. Notice islands
They might be bounded contexts

30. Do it now again

31. Enrich
Let people tell their story
Encourage asking questions
Reverse narrative
Follow the money
Add modelling space

32. Tips
Short kick-off
Make notation visible
Put first sticky yourself
Keep your mouth shut
Guide, not rule
Listen and observe

33. More tips
Cut off fights with hotspots
Attach a problem, not a person
Make alternatives visible
Concur now, divide later

34. Throw away
Your outcome is the
knowledge, not paper roll

35. –Alberto Brandoliny
“Software development is a learning process,
working code is a side effect”

36. References
Leanpub: Introduction to EventStorming
Twitter: @ziobrando
G+: EventStormers
Talks by Alberto and Dan North