Content:

One of the key aspects of Domain-Driven Design (DDD) is the close collaboration between developers and domain experts to ensure that the right thing is developed at the right time.
Domain modeling allows us to explore the specific business domain, enabling us to define bounded contexts for relevant business subdomains. The close exchange between domain experts and developers also facilitates the creation of a ubiquitous language for each identified bounded context.
However, we commonly struggle on the question of how to explore the business domain most effectively. In recent years, however, the Event Storming method has proven to be an effective means to tackle this question.
In our course, we will explore the domain of a fictional company using Event Storming. We will demonstrate how bounded contexts can be derived using Event Storming and how the acquired domain knowledge can be represented as code in a variant of Clean Architecture.

- Workshop includes the following topics:
- Understanding Cynefin Framework.
-- What problem domain are we in? Which tools fit to which domain?
Agile Manifesto, Feedback, Iterative & Incremental Development
- Event Storming
-- Workshop in which we work with a fictitious customer to understand his idea, model it and plan the next steps in an agile way.
- Domain-Driven Development in Nutshell
- Story Narrowing / Splitting
- Hexagonal and Clean Architectures
- Test-Driven Development in a Nutshell
- Ensemble / Whole Team / Mob Programming
- Efficient and secure handling of changes

Disclaimer: The actual course content may vary from the above, depending on the trainer, implementation, duration and constellation of participants.

Whether we call it training, course, workshop or seminar, we want to pick up participants at their point and equip them with the necessary practical knowledge so that they can apply the technology directly after the training and deepen it independently.