This document outlines an introduction to domain-driven design (DDD) through a multi-meeting process using a real-world example. It will involve finding a domain, defining a problem, event storming the domain through brainstorming events and ordering them over multiple passes. Reviews will provide feedback on lessons learned. The goal is to learn DDD concepts through full participation rather than just discussing theoretical examples.

1. Introduction to DDD
Dealing with complexity

2. What is it about COMPLEXITY ?

3. Isn’t this just AGILE 2.0 ?
Agile DDD

4. What do we need to learn in DDD?

5. The way forward…
• Multi-meetup process over several months
• Real world example
• Multiple talk topics – both business and technical
• Not homework or just “Uber-of-x” !
• Full participation

6. Step 1: Finding a DOMAIN
Book exchange Software development

7. Step 2: Defining a PROBLEM
1
Only wearing one hat at a time
2
3
4
56

8. Event Storming the domain (first pass)
@ziobrando
@mariuszgil
@adymitrukBrainstorm events
Order events in timeline
Identify knowledge gaps

9. Event storming instructions:
EVENT
HAPPENED
CAUSE
QUESTION

10. Review / feedback /retrospective
• What went well
• What went wrong
• Lessons learned

11. Event Storming the domain (second pass)
Address knowledge gaps
Reorder events in timeline
Identify subdomains or bounded contexts

12. Review / feedback / retrospective
• What went well
• What went wrong
• Lessons learned