When: October 3-5, 2018
Where: Edinburgh, Scotland

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 event storming 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 event storming. We will use example mapping and feature mapping to get more insights into our process. The outcome can drive our software modelling event storming and create executable specifications.

Kenny Baas-Schwegler - Software Engineer Consultant

Kenny BKenny Baas-Schwegler is a Software Engineer and Consultant focusing on software quality at Xebia. He mentors teams by using practices like Domain Driven Design, Behaviour Driven Development, Test Driven Development and Continuous Delivery. He is an advocate for collaborating in open spaces. By using techniques such as Example Mapping and Event Storming, to engineer requirements and design of software along with business- and stakeholders. With these methods, he aims to create a transparent collaborative domain space with constant and instant feedback of the software that is being built.

Follow Joost van Wollingen at Twitter Follow Kenny