Three years ago, I was at the O'Reilly Software Architecture Conference in Berlin.
There I attended a training session on Event Storming, after which I became interested in the approach and read the book of the same name by Alberto Brandolini, the author of the approach itself.
Impressions from the book are positive, but, as they say, there are a number of nuances. First on the pluses: The author offers an interesting mechanics of the work of a group of people at the workshop for building models There are three levels of models: large picture, process model, system design. Levels are arranged in drill down order The proposed notation is very simple and clear, plus it is introduced gradually and adjusted by the facilitator for the audience. If we talk about the book itself, then the most delicious is located in the first few chapters, where the author talks about the problems: Writing software is not difficult because it is difficult to write code. Writing software is difficult because it is not always clear what exactly needs to be automated. Many people have their own idea of what a big picture of what is happening in the organization looks like, have their own view of the processes, etc. Then the guys who write the code encounter these ambiguities in the process of writing the code and solve them whenever possible. In the end, it’s not what everyone expected. The author makes a logical conclusion that before developing something, it would be cool to understand why and what. And for this, well suited workshops event storming. The disadvantages of the book are that It is in the process of writing and is not yet finished. (As far as the author is concerned, it will never be) The book has duplications, self-repeats and inconsistencies The book looks like an olive salad.) In general, the book about event storming is interesting as the event storming itself:) I recommend it. And for a brief introduction, you can use Alberto’s speech at the Goto conference in Amsterdam. 2018 year-- https://youtu.be/NGXl1D-KwRI
P.S. I loved the Software Architecture Conference and I loved it. 3 A couple of years ago, I wrote more about what
#Architecture #SoftwareArchitecture #SoftwareDevelopment #EventStroming #DDD