How to Capture the Outputs of an Event Storming Workshop?
Event Storming builds ‘shared understanding’. This is often not enough to bring key action-oriented people in! Here are concrete techniques to convince them.
Recent Posts
Event Storming lessons from Post-It haters
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!
How to use Event Storming to introduce Domain Driven Design
Although incredibly effective, DDD is overlooked by developers because of its abstractness. Event Storming is a great way to introduce DDD without naming it!
10 Pair Programming Best Practices Questions & Answers
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.
You should refuse to develop what you don’t understand
Understanding is key to building quality software. Here are 3 levels of understanding we should go through before we start coding.
A serious game for learning ‘built-in quality at the source’
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.
How to max out DDD Big Picture Event Storming with other Workshops
DDD Big Picture Event Storming is a prelude and catalyst to other workshops. Ex: Design Level Event Storming, Example Mapping, Story Mapping & Impact Map...
Feature Teams vs Component Teams? Decide with Event Storming and DDD
Team organization is tough. Event Storming builds enough shared knowledge and architecture for successful team re-organization workshops.