About this Case Study
To really understand what our users will need, we want first-hand experience from 'real-life stories' before we can model and create our software. While both the DDD and BDD techniques place 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 and feature mapping, we can create more insights. We can simultaneously create a model and executable specifications for our user needs. This way, we can write software and tests that match the shared understanding of the user, creating a ubiquitous language. Value will be shipped at a faster pace.
In this session, I will explain how to do process EventStorming. We will use example mapping and feature mapping to get more insights into our process. The outcome can drive our software modelling EventStorming and create executable specifications.
About the Speaker
Kenny Baas Schwegler is a software engineer and consultant focusing on software quality at Xebia. He mentors teams by using practices and techniques from domain-driven design, behaviour-driven development, test-driven development and continuous delivery.
He is an advocate for collaborating in open spaces. He uses techniques such as feature mapping, example mapping and EventStorming to engineer requirements and design software along with businesses and stakeholders.
With these methods, he aims to create a transparent, collaborative domain space with constant and instant feedback on the software being built.
Besides his daily work, he also organises meetups for Behaviour Driven Development NL and Domain Driven Design NL.