Introduction to one of the most recently developed techniques for collaborative modelling that has taken the DDD community by storm (pun intended).

1. #10: Event Storming
(with hands-on
practice)
DDDGreece

2. Shared Mental Model
Why do we need a
shared model?
Why is it so important?

6. Domain-Driven Design is
more agile than agile is!

7. Benefits
Faster time to
market
More business
value
Less waste Easier maintenance
and evolution

8. But how can we do
this?

9. Guidelines
Events
Focus on Business Events
and workflows rather than
data structures
Partition
Partition the problem
domain into smaller sub-
domains
Model
Create a model of each
subdomain in the solution
space
Language
Develop a common
language (Ubiquitous
Language) that is share
and used everywhere in
the code

10. Business Events
Static data is useless
What triggers an
employee to start working
with that data and create
value?

11. Business Events
An outside trigger A time-based trigger An observation

12. Business events are called Domain
events
Are always written is past tense – something
happened – because it’s a fact that can’t be
changed.

13. Event Storming
A collaborative process for
discovering business events
and their associated
workflows

14. Event
storming
ingredients
A room
with wall
space
Paper
roll
Sticky
notes
The right
people

15. People
Development Team
Domain Experts
Stakeholders

16. People
ANYONE WHO HAVE AN INTEREST
IN THE SUCCESS OF THE PROJECT
ANYONE WHO HAS QUESTION
AND ANYONE WHO HAS ANSWERS

17. Benefits
A shared
model of the
business
Awareness of
all teams
Finding gaps
in the
requirements

19. Thank you!
@antonios.klimis
• We are hiring at Bewise.gr
• Web author (HTML, CSS)
• Full stack Developer
• Microsoft Dynamics Developer

20. References
The presentation is mostly based on chapter 1 of the book “Domain
Modeling Made Functional: Tackle Software Complexity with Domain-
Driven Design and F#” by Scott Wlaschin
https://www.amazon.com/Domain-Modeling-Made-Functional-
Domain-Driven/dp/1680502549
Highly recommended!