Event Storming builds ‘shared understanding’. This is often not enough to bring key action-oriented people in! Here are concrete techniques to convince them.
After going through why Event Storming uses post-its, we’ll go over alternatives. We’ll then see how to use these techniques to improve Event Storming!
Although incredibly effective, DDD is overlooked by developers because of its abstractness. Event Storming is a great way to introduce DDD without naming it!
Pair programming is not just sitting together in front of an IDE. Here are battle tested answers to common questions that will make pairing work for you.
Understanding is key to building quality software. Here are 3 levels of understanding we should go through before we start coding.
Skip studying queuing theory! Play this 1h15 serious game for learning why building-in quality at the source leads to a productive and sustainable pace.
DDD Big Picture Event Storming is a prelude and catalyst to other workshops. Ex: Design Level Event Storming, Example Mapping, Story Mapping & Impact Map...
Team organization is tough. Event Storming builds enough shared knowledge and architecture for successful team re-organization workshops.