Downloaded 141 times
More Related Content
Event storming
- 1. COLLABORATIVE LEARNING FOR COMPLEXDOMAINS EVENTSTORMING @thepaulrayner Paul Rayner
- 2. THE LANDSCAPE Complex businessrules & processes Knowledge silos Numerous diverse (& often legacy) system interactions
- 3. THE CRITICAL COMPLEXITYOF MOST SOFTWARE PROJECTS IS IN UNDERSTANDING THE DOMAIN ITSELF Eric Evans
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10. PLACE EVENTS ON ATIMELINE
- 11.
- 12. WHAT IS ADOMAIN EVENT? Something that happened in the business that your domain experts care about
- 13.
- 14. SPECIES OF DOMAINEVENTS • A step in a business process e.g. customer order submitted, customer paid $100, order completed, item shipped. • Something that happens on a scheduled basis e.g. nightly account reconciliation completed, end of month. • Something meaningful that occurs as a result of something else happening e.g. customer account locked after invalid password entered 3 times
- 15.
- 17.
- 18.
- 19.
- 22.
- 23. Development team membersand business people gather in a room and together we create a visual map of the flow of events
- 24.
- 28.
- 31.
- 32.
- 33. They lived happily ever after Once upona time… More modeling space than you expect
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 43.
- 46.
- 47.
- 48. Decided to Reimburse(alternate flow) Decided to Repair (main flow)
- 49.
- 50. Event Stream … ECommerce Context EventStream … Order Management Context
- 51.
- 52. EVENTSTORMING FACILITATION TIP#1 Focus first on learning and understanding
- 53. CLARIFYING QUESTIONS ‣ “Whatcircumstances would cause ... to happen?” ‣ “What was the path that led us here?” ‣ “What is a good example of …?”
- 54. CLARIFYING QUESTIONS ‣ "Whatdo you mean by …?" ‣ "What might lead someone to do/need …?” ‣ "What else might happen…?
- 55. EVENTSTORMING FACILITATION TIP#2 Anchor to a concrete business example
- 56. EVENTSTORMING FACILITATION TIP#3 Clarify fuzzy concepts and language
- 57. Command is “OpenClaim” What should associated event be called?
- 58. EVENTSTORMING FACILITATION TIP#5 Conversations and examples are primary
- 59. EVENTSTORMING FACILITATION TIP#6 Post first, Ask questions later
- 60. EVENTSTORMING FACILITATION TIP#4 Timebox
- 62. POSSIBLE LIMITATIONS ‣ Simplebusiness domains (e.g. CRUD) and/or systems ‣ Distributed teams ‣ Larger group/greater complexity = better facilitation ‣ ???
- 63.
- 65. WHY EVENTSTORMING? Collaborative learning Cultivatemutual shared understanding Uncover misunderstandings & missing concepts Avoid rework
- 66. WHY EVENTSTORMING? Model &explore complex domains Visual, tactile representation of system behaviour & outcomes Smoother transition to a rich domain model, design and coding
- 67.
- 68.
- 69.