I have been asked why the majority of my articles around EventStorming use the name EventStorming as opposed to Event Storming.
Ok, I realise this may seem like bike shedding but I have good reason for being particular about what I call the series of workshops created by Alberto Brandolini.
I try not to use Event Storming but when I do I typically refer to a brainstorming exercise run as part of a discovery workshop. At its most primitive, you will capture processes through a set of events ordered along a timeline.
However the workshops described by Alberto Brandolini and discussed in my articles go beyond this exercise and include more structured modelling exercises and prioritisation and scoping techniques. I interpret EventStorming as three distinct workshops, Big Picture, Process modelling and Software Design and they each tackle the challenge of capturing requirements in different ways. For this reason, when I discuss the workshops I use the name EventStorming, and I deliberately avoid using Event Storming so as not to confuse the two.
Furthermore I adopted the moniker after noticing that Alberto Brandlin's literature will often use the name EventStorming. In fact the actual title of his book is Introducing EventStorming, and in the preface you will find EventStorming six times and not a single hint of Event Storming.
Anyway I hope that's all clear now. Thanks for reading and if you would like to know more about EventStorming then you could try reading my overview article EvetStorming - What's it all about? or my facilitator's guide to process modelling EventStorming - How do I model process?
