When: january 31th, 2018
Where: Amsterdam, Netherlands
To really understand what our users will need, we want to have a first-hand experience from 'real-life stories' before we can model and create our 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 based on feature mapping, such as Example 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 which matches the shared understanding of the user, creating a ubiquitous language. Value will be shipped at a faster pace.
In this hands-on session, we start with a Process EventStorming. We will use Example Mapping to get more insights into our process. Eventually, I will show you how the outcome can drive our Software Modelling EventStorming and create Executable Specifications. This way we can create a ubiquitous domain language that we can use in our application and test code. You don't need a laptop for this session as the focus is on the discovery phase.
Kenny Baas-Schwegler - Software Engineer Consultant
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.
João Rosa - Software Consultant
João Rosa is a Software Developer, focused on delivering quality software that matters. Believes in the software crafts to provide software in sustainable peace; he is a DDD, BDD and TDD practitioner. Can't live without his CI/CD pipeline
During his career he always pushed the teams and himself to improve the communication, reducing the gap between developers and the business.