Please log in to watch this conference skillscast.
To really understand what your users will need, you want to have a first-hand experience from 'real-life stories' before you can model and create your software. While both the DDD and BDD techniques emphasis on ‘real-life stories’ by doing collaborative deliberate learning, they both focus on different goals. DDD focuses more on creating bounded contexts in which a single model is created, BDD focuses more on different scenarios and can create executable specifications as an outcome.
By doing EventStorming and using techniques from BDD, such as Example Mapping or Feature Mapping, you can create more insights. You can simultaneously create a model and executable specifications for your user needs. This way, you can write software and tests which matches the shared understanding of the user, creating a ubiquitous language. Value will be shipped at a faster pace.
In this session, Kenny will explain how to do Process EventStorming. He will use Example Mapping, or Feature Mapping to get more insights into his process. The outcome can drive your Software Modelling EventStorming and create Executable Specifications
YOU MAY ALSO LIKE:
- Towards Autonomously aligned teams with Domain-Driven Design (SkillsCast recorded in October 2019)
- Domain Models in Practice: DDD, CQRS & Event Sourcing with Marco Heimeshoff (Online Course on 28th September - 2nd October 2020)
- Retrospectives Antipatterns — Team Meetings That Don't Suck (SkillsCast recorded in July 2020)
- Applied Domain-Driven Design — Full-Stack Event Sourcing (SkillsCast recorded in July 2020)
Crunching 'Real-Life Stories' with DDD Event Storming and Combining it with BDD Techniques
Kenny Baas-Schwegler is a strategic software delivery consultant, Socio-technical architect, facilitator, collaborate modeller, technical lead that builds quality into software delivery at Xebia. He mentors, coaches and consults management and teams by using practices, techniques and tools from domain-driven design, anthropology, deep democracy, behaviour-driven development, DevOps, and Continuous Delivery.