Event Storming - Alberto Brandolini - DDD Europe 2019

[@nnmartin94]

Maybe Disney should have used this process to write better Star Wars sequels. Great talk!

[@tolgatalas9546]

hahahahahah

[@nuscly]

Definitely a very efficient solution to discover the domain, align people and fight the bullshit 👏

[@darkomaksimovic3456]

Spoiler alert, he doesn't get a stroke at the end

[@jordanbeagle5779]

Damn, this guy is a really good speaker! Great talk!

[@GP-ez5ms]

He is the author of event storming :) Talking about it for >10 years

[@abdelmounaimelhili4537]

Great content.

[@deyan.todorov]

Great presentation!

[@MichaelCampbell-np4wj]

If only we could have seen the beginning of it. Watching him walk around on stage was interesting, I guess.

[@AnkitTannaVlogs]

I liek this talk but I am not sure if orgalisations are so siloed in today's time.

[@MichaelS-zg1nn]

Working at a global enterprise I can assure you silos are pretty much still a thing. I believe it is a problem that grows with the size of the organisation.

[@xetra1155]

I have a hard time bringing this into a existing company with existing software to figure out the domain structure after 1995. Is this even made for legacy companies/domains?

[@OberfeldwebelPfeffer]

Yes it is. A colleague of mine went to a very traditional private bank and did this with the stakeholders and the dev team. Afterwards the owners of the bank told him that even they themselves learnt some new thing about how their company works.

[@mistersunday_]

It all comes down to comprehension. Could've dropped the mic right there and walk away

[@supratipb]

'Outside in vs inside out' thinking is mentioned for Command at 17:16 . What does the statement means? does it mean Command is either of them based on situations or its always Outside in?

[@TomaszKubacki]

I think what he means is that by the very nature of Commad entity (someone give an order to do something vs something happens as in case of events) using Command push you towards customer driven process modeling

[@AhmedEidX]

This is really a great talk, but I am wondering, how the outcome of the event storming workshop is stored to be communicated later to UX/UI designers, Software Architects, and other technical team members in the next stages?, In which form of diagram we can draw the validated results of the event storming session to store it digitally?

[@eglauko]

Well, you can use Miro, or Drawio, to store digitally. If you use Miro, you can create multiple frames, instead of editing the one that already exists, you create a copy and edit that copy. You can create copies for stages (Big Picture, Process Design, Softwares Design) and also for versioning. You can still use other diagrams and visual tools together.

[@xetra1155]

I also wondered if Event Storming can be used as the first initial process and afterwards using Domain Storytelling to refine the events into actual stories

[@BillieThompsonPurpleBooth]

Ideally they would be in the room, participating.

[@marekbugiel6893]

Guy seems to have a lot to say but should have go a little bit slower.

[@StefanEdlich]

He is Italian! Playback speed won't help? ;-)

[@marekbugiel6893]

​@@StefanEdlich I don't mean I could not understand him, rather I'd like him to spend more time on what he says, elaborate.

[@agitkaplan7991]

I think this is DDD people's common problem, they either write long books or they make short not comprehensive presentations. Their techniques might be good but absolutely it is difficult to understand them.

[@pynchia4119]

Do you really say "ridi" instead of "ready"? Do you also say "hider" instead of "header"?