Collecting requirements or understanding a large system seems such a long and demanding activity. We can do al lot better than this: unlimited modelling space and all the key stakeholder in the same room, with some special spice. :-) Domain-Driven Design has never been so efficient. This is where DDD meets Kanban, TOC and Management 3.0.

1. EventStorming
recipes @ziobrando

2. What’s Eventstorming
Let me show you…

3. #CDays14 – Milano 25, 26 e 27 Febbraio 2014
Video!

4. What’s Eventstorming
All the key stakeholders in the same
room
with an unlimited modelling space
using stickies as Domain Events

5. But basically…

6. it’s a party
Let me show you…

7. who should we
call?

12. you missed
the party

13. but also…

14. You’re invited
to the next
one

15. hack the place

20. no sitting

22. Ubiquitous
body
language

24. Domain Events

26. along a
timeline

31. Let the magic
happen!

32. no UML
No BPMN
NO …

33. Model affinity

34. Domain events
are just a
sweet spot

35. next steps

40. incomplete is a
legitimate
state

43. When should we
stop?

44. The real
constraint…

45. Make the party
memorable

46. What are we
seeing
exactly?

47. system view

55. Different
people make a
different party

58. in small
companies…

61. Code coverage?

62. http://www.businessweek.com/articles/2013-04-18/faq-reinhart-rogoff-and-the-excel-error-that-changed-history

65. look for things
that matter

67. who’s with me?

68. gotta do something!

69. are you ready
for it?

70. What about
remote
eventstorming?

72. What about
remote
toga party?

74. Ok, seriously

75. Wrapping up

77. but…

78. leave it
around, for a
while…

80. chaotic eats
sequential for
breakfast

84. Creative
collaboration

85. meaningful
conversation with
domain experts?

86. ©
Alberto
Brandolini
2009
experts
help
us
to
understand
and
we
help
them

87. choose your role

88. Find an
observation point

89. Model
storming?

90. sorry about
that

91. © Alberto Brandolini 2013
Event Storming
expected outcome
steered towards a canonical
model
partially defined steps
model affinity
given problem type

92. © Alberto Brandolini 2013
Model storming
unpredictable outcome
no canonical model
notation incremented
iteratively
!
no predefined problem type

93. Don’t postpone
people

94. questions?

95. Tkanks! @ziobrando

96. References
EventStormers community on Google+
https://plus.google.com/u/0/communities/
113258571348605620818
!
Introducing Event Storming:
http://ziobrando.blogspot.com/2013/11/introducing-
event-storming.html