Event Storming

Transcript

1. JakubPilimon JakubPilimon
2. JakubPilimon Developer, Blogger, Trainer, Eventstormer Loves to tackle complex enterprises with: • Domain-Driven Design • Test-Driven Development • Spring tools Being a microservice freak, architecture is his main area of interest too. Here is his DZone MVB awarded blog: pillopl.github.io Co-founder of #dddbyexamples initiative: github.com/ddd-by-examples SPRING DEVELOPER ADVOCATE AT PIVOTAL
3. JakubPilimon Code to a developer is what a scalpel is to a surgeon
4. JakubPilimon “The critical complexity of most software projects is in understanding the domain itself” Eric Evans
5. JakubPilimon
6. JakubPilimon
7. JakubPilimon
8. JakubPilimon - Gimme requirements 
 - I will translate them to code - I will get back with questions because business guys know … the business
9. JakubPilimon • In every organization knowledge is a distributed thing • There are silos • …But business flow crosses the silos and expertise boundaries • There is a need to have a common narration of what we actually do or want to do • … and big design up-front does not work
10. JakubPilimon Alberto’s book
11. JakubPilimon Alberto’s book
12. JakubPilimon And it’s both IT’s fault and domain experts’ fault! COMMON NARRATION! UBIQUITOUS LANGUAGE! … so we need a cross-perspective, lightweight technique to find/build those
13. JakubPilimon “It’s developers (mis)understanding, not domain experts’ knowledge that goes into production” Alberto Brandolini
14. JakubPilimon
15. JakubPilimon Alberto’s book
16. JakubPilimon Alberto’s book
17. JakubPilimon • Reverse narration will enforce timeline, find missing events and start conversation about compensating events • Structure starts to show -> people, actors, external systems, boundary of our system, risk Alberto’s book
18. JakubPilimon Alberto’s book
19. JakubPilimon
20. JakubPilimon
21. JakubPilimon github.com/mariuszgil/awesome-eventstorming
22. JakubPilimon • Actors (people, systems, external systems) are clear - structure is clear • Knowledge is distributed, common narration in place, silos broker, ubiqitous language in place • Massive learning about what we do • Core problem consensus • Risks displayed • Misunderstandings discovered • Opportunities found Big Picture Event Storming
23. JakubPilimon • Simple notation • No exposure to software • Cross-perspective: lean, agile, ux, business, development - no-one is excluded • Green field of legacy • And… it’s fun • And … for free • And ... no need to change anything! Big Picture Event Storming
24. JakubPilimon • Business metrics • 2 things, one name • 1 thing, 2 names • No need for development • No way for development! • If you eliminate this, that will be eliminated … and the feature is there • “What if that does not happen?” - cause-effect relationships • Does state matter? Or events? • Find inconsistencies in current software My Event Storming War Stories
25. JakubPilimon • Big Picture Event Storming - for kickoff • Design Level Event Storming - for software modeling • UX-Driven Event Storming - to focus on Customer Journey, usability, holes, etc. • Event Storming as Retrospective - to look for improvement • Event Storming as a Learning Tool - for new hires Event Storming
26. JakubPilimon “Software development is a learning process. Working code is a side effect. Alberto Brandolini
27. JakubPilimon Books • Introducing EventStorming, Alberto Brandolini • Domain-Driven Design Distilled, Chapter 7: Acceleration and Management Tools, Vaughn Vernon Articles • Introducing EventStorming, Alberto Brandolini • Facilitating EventStorming, Mathias Verraes • An introduction to EventStorming: The easy way to achieve domain-driven design, Steven A. Lowe • Modelling Reactive Systems with EventStorming and Domain-Driven Design, Kevin Webber • EventStorming: On Fake Domains and Happy Paths, Mathias Verraes • EventStorming Exercise, Tim Schraepen • Event Storming and Spring with a Splash of DDD, Jakub Pilimon • EventStorming's Coincidence with Business Process Improvement • EventStorming, What You Need to Know, Daniel Whittaker Resources github.com/mariuszgil/awesome-eventstorming