At first look, EventStorming is deceptively just have a long paper roll available, and a virtually unlimited stock of coloured sticky notes and start modelling problems that looked too big to be modelled. But the ability to visually mastering large scale complexity opens the way to many interesting outcomes.
- Better business once you see the process, impediments and correlations are vividly displayed. You can't avoid tackling them.
- Better software see the areas where stakeholders needs are in conflict, resolve coflicts by leveraging bounded contexts.
- Better exploration of complex domain is now question-driven and with a visible collective sketch. Your team will never be so wise.
- Better trigger the right conversation between the right people.
In this book you'll find guidance about how to leverage the potential of EventStorming.
At the time of writing, the book is still being written, so I cannot give it a fair rating yet.
However, the book shows great promise for people looking to facilitate eventstorming. It explains how and why eventstorming works, and has plenty of interesting tidbits on people skills to use during facilitation. I liked how it explained the use of eventstorming for both high level exploration as well as detailed technical analysis.
Interesting concept of capturing business events (hence the name "Event storming"). There are a few interesting ways to use the tool (called grammars). Unfortunately the success of the event is highly dependent on the skill of the facilitator (in both knowing the tool and how to guide the room towards productive behavior) and the commitment of the org (to have business representatives looking at the problem from the process perspective)
Also a bit of a shame that the book is not finished.
A témát (EventStorming módszertan) ismerem blogposztokból és videókból, használtam is különböző variánsait, de most egy közeljövőbeli megbízás miatt a könyvet is megvettem, és egyben végigolvastam. Az EventStorming az általam ismert leghasznosabb szervezet-, folyamat- és termékfelderítési módszertanok egyike, Alberto stílusa remek, az illusztrációk sokat segítenek - akkor miért a mindössze 3-as értékelés?
A legfontosabb indokom, hogy a könyv egyszerűen nincs készen. A szerző nem hallgatta el ezt a tényt, a LeanPub kiadónál megvásárolható kiadvány leírásában még az egyes fejezetek százalékos készültségét is feltüntette, szóval nem zsákbamacskát vásároltam. De a számokból nem látszott, hogy rengeteg az ismétlés, a szöveg gyakran a mondat közepén szakad félbe, és bizony egy olvasószerkesztő is elkelt volna. A kidolgozatlan fejezetek aránya (és a kidolgozatlanság mértéke) a mű vége felé haladva egyre nőtt, pedig nekem pont azok a részek lettek volna fontosak.
Az árazás is érdekes. Eldönthettem, mennyit szeretnék fizetni: a licit 19,99 dollárról indul, és lehet akár csökkenteni is - de csak 9,99 dollárig. Azon gondolkodtam, hogy a félkész könyv eladásra kínálása helyett egy Kickstarter-kampányt kellett volna indítani - szívesen befektettem volna ennyi vagy akár több pénzt, hogy egyszer majd megkaphassam a befejezett művet. Így azonban valószínűleg még egyszer meg kell majd vásárolnom, amikor Alberto elkészül vele.
Összefoglalva: az osztályzat nem a témának és nem is a szerzőnek szól, hanem a konkrét kiadás megvalósításának. Sajnálom, hogy ilyen lett.
EventStorming is a powerful and versatile tool, not only in the tech space. First and foremost, it's a way to map any complicated process. As a visually driven person, this appeals to me a lot; no software has ever beat simple pen and paper when it comes to flexibility, speed, and focus.
The approach itself is inspired by User Story Mapping - a related, and also very useful concept.
While I value the ideas in the book tremendously, as well as the author's deep experience (years and years of consulting large and small co's), the writing is just painful to follow. It's obviously by design – the book is unfinished (perhaps it will never be). But I feel like a short, well-written guide plus some YouTube recordings would be a much better way to learn the book's concepts than reading the original.
That said, I admire the author for releasing this in whatever form (ship early!) to share with the world, rather than waiting months or years to have a polished version (ideas >> form).
While the edition from LeanPub is unfinished, it contains a wealth of information to get started with EventStorming. From explaining the process, the supplies, patterns and anti-patterns, and describing the facilitator's role and observation, there is a lot on how the EventStorming process works and what it could be used for.
I initially got this book to peek at a process that reminded me of many of the Agile processes I learned ages ago. This book solidified my suspicions and gives me more to run with for other applications not covered in this book.
If this were a completed book, I could see this getting to 5 stars. It's only at 4 stars because there are a bunch of incomplete sections. Again - well worth it even in its incomplete state!
It's chaotic, and it's not ready, it's not well-written, it's full of small mistakes. On the other hand, its full amazing and priceless insights have many heuristics, raw and opinionated (which is good IMHO).
It is the only and best position about the topic. It is definitely recommended if you are interested in that topic, plus - as a bonus - if you like to peek inside someone's brain, that's a perfect position to read.
It’s a interesting practice, which I’ve tried using at work with limited success. It felt simple enough to start, but I think you need good facilitation skills to effectively make use of it.
The book isn’t complete, with lots of todo’s and fixme’s throughout it and hasn’t been updated for over a year. However, I felt it contained the core details to understand EventStorming.
This is one of the best books I’ve read in the last five years about software development and how to learn collaboratively. It’s not finished yet, but it’s full of well reasoned opinions and great advice.
At the time of finishing this on LeanPub Alberto calls the book 70% complete. Based on what I have seen so far I am giving 5 stars, and will re-read and update my review once the book is complete.
The core content is a great introduction to event storming, but much of the content is incomplete and later chapters are restatements of earlier chapters.
When you start working in projects, if you're good, you know all the theory.
EventStorming is a book that dive deep in the 'How exactly?' part of the question.
Being a draft (literally, this is draft-edition) the book is a methaphor of the methodology: once flexible, even incomplete, it is a powerful and essencial tool to cut through the modern business complexity.
Personally, I think that I will use this tool when closing a project, in the phase of lessons learned.
I'm grateful for the possibility to read the unfinished book (see leanpub.com). Some fragments are even marked as 2% completed. Others 20, 50, 80 and 100% ready. Nevertheless - there's a huge added value behind the book.
Before my 1st Event Storming workshop, I thought that it's a new label for Brainstorming. Now - it's one of the most powerful tools for the 1-2 days workshops. (In the book I found also 2hours long workshop example). With Event storming it is easy: Discovering tacit knowledge, do the know-how transfer, optimize the processes & work; highlight the troublesome areas with the most added value behind. And all of that can be done with the experts from different areas (like subject matter experts, lawyers, SW developers, testers, architects, product owners, business people, etc.). That saves tons of time (even if sometimes it looks not 100% productive).
In the book - a theory behind, with good and bad practices.
P.S. At the end - when that book will be 100% ready, it can be 3, 4 or 5 star material. Yet, now I consider the added value is the highest. You can get the added value - before Event Storming is included in a "Business as usual" practice.
Learnings from participating in Event Storming Sessions
> This is a phenomenal tool, specially for creating safe knowledge sharing space. It makes most important problems visible! > Things that I saw as super important -> having an experienced facilitator to keep things flowing and marking the possible hotspots -> having some pivotal events before starting to minimize the organizing effort later -> different wording for the same events are a super clear indication of different bounded contexts -> this facilitates a lot finding your bounded contexts -> when discussing events at the boundaries of each bounded context, you don’t need to agree on language. There is a ton of value in just making this disagreement visible.