Introduction to Event Storming
Download as PPTX, PDF6 likes3,474 views
The document discusses the methodology of event storming in domain-driven design, emphasizing collaboration between domain experts and stakeholders. It outlines the importance of creating a conducive modelling space for effective communication and knowledge sharing, while also providing practical tips for facilitating these sessions. Key themes include the iterative nature of the process and the significance of visual notation to aid understanding.
Introduction to Event Storming
- 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
- 8. EventStorming People with questions Meeting people with answers In one room Plus…
- 10. Unlimited
- 11. Notation
- 12. Simple
- 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
- 25. One picture That explains it all Image credit: Alberto Brandolini
- 27. There is something in between your stickies
- 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