Creative Photography: Food, Rooms & People

📜Timetable📜

• 🕡18:30 Welcome
• 🕖19h Talk
• 🕗20h Snacks and drinks

💬Talk: Der Bounded Context – Malen wir ihn in ein Canvas 💬

Bei der Signal Iduna coachen wir die Teams bei der Entwicklung von Softwaresystemen. Dabei modularisieren wir im Rahmen des strategischem Domain-driven Design unsere Anwendungsdomäne in Bounded Contexts. Um diese anschließend auf einer groben Ebene zu beschreiben, nutzen wir das BoundedContextCanvas (BCC) der ddd-crew. Wir möchten in diesem Vortrag das BCC als Artefakt vorstellen und unsere Erfahrung bei der Vorgehensweise und die Auswirkungen auf das Unternehmen mit Euch teilen. Weiterhin stellen wir Euch eine Lösung vor, in der die Ubiquitous Language durchgängig in unterschiedlichen Artefakten sichtbar und auffindbar wird.

🗣️Speaker: Kai Rüstmann🗣️

Kai Rüstmann arbeitet seit vielen Jahrzehnten in der Softwareentwicklung und bevorzugt ein agiles Arbeitsumfeld. Ein Großteil dieser Zeit durfte Kai als Consultant unterschiedliche Anwendungsdomänen kennenlernen. Dabei war ihm neben guter Software-Craftsmanship stets ein großes Anliegen, die Anwendungsdomäne zu verstehen und die Software daran auszurichten.
Mittlerweile ist Kai seit einigen Jahren in der Versicherungsbranche tätig und versucht dort in einem großen Unternehmen mit hohen regulatorischen Anforderungen, Themen wie agile Softwareentwicklung, Domain-driven Design und Team Topologie in Einklang zu bringen.

📜Timetable📜

• 🕡18h Welcome
• 🕖18:30h Interactive talk
• 🕗20h Snacks and drinks

💬Interactive Talk: Knowledge Crunching and Psychological Safety—from Myth to Evidence-Based Practices💬

Do you know the situation of having an urgent question in a meeting in order to be able to follow the rest of the meeting well, but not daring to ask it? Have you ever held back information in a conversation because you were not one hundred percent sure of its relevance or accuracy? Perhaps you have also experienced a reverse situation in which you expressed your opinion and afterwards you realized that it was simply accepted, although you would have liked to have had a critical reflection yourself?

In case you answered one of these questions with yes, be assured that this not uncommon. However, it may take away an opportunity to learn together and create clarity. Speaking of Domain-Driven Design, this especially applies to Knowledge crunching, the collaborative gathering and discovery of all relevant influencing factors in order to build a useful model. Knowledge crunching is an essential starting point and continuously guiding part of Domain-Driven Design throughout the whole process. In order to be successful to collect the relevant insights, all participants have to feel safe and need to have the opportunity to contribute their knowledge and experience. Which leads us to the topic of psychological safety.

With the release of the famous New York Times article “What Google Learned From Its Quest to Build the Perfect Team” it is widely known that psychological safety is a valuable aspect in team collaboration with major effects on team performance. Since then, psychological safety has become a hyped topic and is often sold as a panacea (universal cure) for “underperforming” teams. Despite existing scientific knowledge about how psychological safety functions and how it is created, people started to use own interpretations and tried to create it by fighting symptoms rather than implementing meaningful changes. This lead to many misunderstandings, myths surrounding psychological safety and, as a result, the topic is often seen as ineffective at best or, at worst, even as a harmful promotion of a performance-averse feel-good oasis.

In order to be successful as a practitioner of Domain-Driven Design when working with socio-technical systems, you will have to deal with psychological safety. This workshop will support you by going back to the scientific knowledge and you will learn:

• why and in which environments psychological safety is important in the first place,
• that psychological safety is always context-dependent,
• why uncertainty is naturally the default in many situations,
• why everyone involved is needed for psychological safety to emerge, and
• some quick fixes that work on a systemic level and which are not just symptom avoidance interventions.

You don’t need any prior knowledge to take part in the session. In the interactive parts, we will give you the opportunity to reflect on what you have learned for your personal contexts and to exchange insights with other participants. At the end, you will take away at least one idea for a first step to improve the conditions for the development of psychological safety in your own environment.

🗣️Speakers: Helen Rapp and Martin Günther🗣️

Helen is a psychologist and has been supporting teams and organizational units in learning together for several years, for example in the role of an agile coach. She uses her training, her systemic approach, and her experience in designing and facilitating collaborative workshops to make collaboration effective and at eye level. In her work, she pays particular attention to the people in the organization without losing sight of the big picture.

📜Timetable📜

• 🕡18:30 Welcome
• 🕖19h Talk
• 🕗20h Snacks and drinks

💬Talk: QualityStorming: Collaborative Modelling for Quality Requirements💬

In various communities, several methods for the collaborative modeling of business requirements have been established in recent years. Well-known examples are EventStorming or Domain Storytelling. These approaches are based on achieving a better shared understanding of the business requirements in an interdisciplinary way. But what about the requirements for the quality of the software being developed?

This is where Quality Storming comes in, trying to bring together a heterogeneous set of stakeholders of a product or project to collect quality requirements. The goal is to gain a shared understanding of the real needs for the quality characteristics of a product. To achieve this goal, Quality Storming uses some techniques from various already existing collaborative modelling approaches.

It is not the claim to produce perfectly formulated quality scenarios with the help of Quality Storming. Instead, the method aims to create a well-founded, prioritized basis for later formalization, which is understood across different stakeholder groups. The more often teams work with the technique, the better the quality of this basis becomes over time. Advanced teams are quite capable of creating very well-formulated scenarios within the framework of such a workshop.

In this talks I will introduce the workshop and the ideas behind it. You will also learn many hints for facilitating such workshops and how to proceed with the learnings generated in Quality Storming workshops.

🗣️Speaker: Michael Plöd🗣️

Michael works as a Fellow for INNOQ in Germany. He has over 15 years of practical consulting experience in software development and architecture. His main areas of interest are currently Domain-driven Design, Microservices and in general Software Architectures. Michael is a regular speaker at national and international conferences.

📜Timetable📜

• 🕡18:30 Welcome
• 🕖19h Talk
• 🕗20h Snacks and drinks

💬Talk: Fighting Technical Debt with DDD💬

Great technologies, programming languages and tools are used when building software. That is good and right. But unfortunately, it is often lost sight of the fact that the decisive factor is not the technology, but the business domain. If we do not map the domain language and the business processes in the software, then it will not help our users in their work. No technology in the world can protect us from this.
In this talk, I’ll show you how you can identify problems in an existing legacy system that could be solved with Domain-Driven Design. We will see problems such as: large entities that are used all over the system, how we could divide them into smaller entities according to the business domain and how we should cut the source code into bounded contexts. All this will be done with many examples from analysis tools that help us to see the system on the level above the source code.

🗣️Speaker: Carola Lilienthal🗣️

After the pandemic we will restart the meetup with an in-person event with an intro to DDD.

Timetable:

• 18:30 Welcome
• 19h Talk
• 20h Pizza and Glühwein

💬Talk: Introduction to DDD—It’s All About the Domain, Honey💬

To build software, we use great technologies, programming languages, and tools. And we have a lot of fun programming in this technical environment. But we must not forget that the most important point for a successful project is not the technology but the domain! To understand the domain we need a common language with the domain experts. Also, if we don’t reflect the domain model in the software and its architecture, it will not help our users doing their work.

It is easy for developers to fall into the trap of focussing on technology instead of the domain. To prevent you from this, I will show in this talk how Domain-Driven Design (DDD) can help you to gather the domain knowledge and transform it into a Ubiquitous Language. To do this we use techniques like Interviews, Domain Storytelling, and Event Storming.

In practice it is not easy to decide how to divide up the domain and develop microservices for it. Here the DDD pattern Bounded Context can help us. It shows us where vertical cuts can be made.

Using these tools together with the Building Blocks of DDD enables us to build an architecture that represents the domain and makes our users happy.

🗣️Speaker: Henning Schwentner🗣️