Modeling a business process is often associated with people in suits having long and dull meetings. Way too much time gets wasted for an outcome that's far from reality and which will be obsolete in weeks. Event storming is a workshop format that brings modeling back to all stakeholders, and aims to create usable models. In this workshop, you won't be writing any code, but you will be using lots of paper, post-its and a marker. After going over a bit of theory and a small example, we will present you with a real business problem, and in a few short playful sessions you will experience how powerful event storming can be in helping a team gain insights into complex problems. The techniques you will learn in this workshop will pay off immediately.

1. EVENT STORMING
WORKSHOP
@JefClaes & @ToJans

2. WHATTO EXPECT?
• Introduction
• Get busy (*)
• Conclusion (*)

3. Modeling?

4. In the enterprise?

9. So no modeling then?

11. What techniques do you use?

12. Let’s create a model! A data model.

13. Let’s create a model! A data model.
(*10 minutes - boring)

14. Can we make this fun and
useful for all stake holders again?

15. Model storming
by @ziobrando

19. Event storming

20. Event storming is a workshop format aiming to
collaboratively create a model of
a complex business flow.
- @ziobrando

21. Setting up..

22. the right team

23. big problem = big space

26. one man = one marker

27. 1. Events

28. Something that happened in the past..
..where our business cares about.

29. Search for events.

30. this
happened

31. Where to start?

32. this
happened
this
happened
this
happened
this
happened
this
happened
this
happened

33.
Mind your language!

34. Customer updated
Customer moved

35. Assumptions (unless..)

36. What if we don’t agree/know?

37. this
happened
that
happened
!
?

38. „All models
are wrong,
some are
useful”

39. Where are these events coming from?

40. 2. Commands

41. Do something!

42. Caused by actors, time or external systems.

43. this
happened
do this

44. 1command == 1 event?

45. this
happened
do this
this
happened
this
happened
do this

46. 3. Bounded contexts

47. Where the language is consistent.

48. BC 1 BC 2

49. In conclusion

50. visualization

51. collaboration

52. discovery

53. the big picture

54. viable model

55. https://plus.google.com/communities/
113258571348605620818

56. Thank you!
@JefClaes & @ToJans
Feedback?