Model Storming.
Building a software system is in fact a learning process. Unfortunately we don’t know much about learning even if we’ve been doing it for all our lives. A different approach on discovery of domain complexity could help our teams to understand, frame and master the problem and solution space, enhancing collaboration with the domain experts and the stakeholders and bringing some fun.
This implies breaking some rules and assumptions, doing something unconventional, and occasionally feeling stupid. Are you ready for it?
YOU MAY ALSO LIKE:
- Alberto Brandolini's EventStorming Workshop (in London on 13th - 14th November 2019)
- The Gordian Knot (SkillsCast recorded in May 2019)
- Advanced Docker for Enterprise Operations (in London on 23rd - 24th September 2019)
- CloudNative London 2019 (in London on 25th - 27th September 2019)
- Running Stateful Applications in Kubernetes (in London on 5th September 2019)
- Domain Models in Practice: DDD, CQRS & Event Sourcing with Marco Heimeshoff (in London on 18th - 20th September 2019)
- Strategic DDD & Sociotechnical Architecture with Kacper Gunia and Nick Tune (in London on 30th September - 1st October 2019)
- P3X - People, Product & Process eXchange 2019 (in London on 31st October - 1st November 2019)
- Domain Driven Design London September (in London on 9th September 2019)
- Domain Driven Design in Practice with Helin Ece Akgul (SkillsCast recorded in August 2019)
- But What About the UI? (SkillsCast recorded in May 2019)
Model Storming.
Alberto Brandolini
Alberto Brandolini can model every business domain, given enough space, a paper roll and an unlimited source of colored sticky notes (with a preference for orange ones). He calls this stuff EventStorming.
Model Storming.
Alberto Brandolini
Alberto Brandolini can model every business domain, given enough space, a paper roll and an unlimited source of colored sticky notes (with a preference for orange ones). He calls this stuff EventStorming.