Domain Storytelling

Domain storytelling is a practical and user-centered method in which users and developers work together. The simple, visual representation of often complex contexts helps to develop a deep understanding of the development goals and problems. This eliminates misunderstandings at the start of development, which saves costs, time and hassle in the long term and boosts quality. Henning is an expert and consultant and tells us what domain storytelling looks like, how and where it is used and what the limits of this method are.

“The user tells the business analyst, the business analyst tells the architect, the architect tells the developer (…) and in the end something is built that has nothing to do with what should be built here in front” - Henning Schwentner

Henning Schwentner loves high-quality programming. He lives this passion as a programmer, trainer and consultant at WPS - Workplace Solutions. There he helps teams to restructure their monoliths or to develop new systems with a sustainable architecture from scratch. Henning is the author of Domain Storytelling (Addison-Wesley, 2022), Domain-Driven Transformation (dpunkt, 2023) and the LeasingNinja.io.

Highlights of this episode:

• Henning Schwendner talks about domain storytelling, a method for improving understanding between users and developers
• Domain storytelling helps to overcome the media discontinuity in software development
• Henning has published a book on the subject of domain storytelling
• There is a prize draw for three signed copies of the book
• Domain storytelling is practiced through graphical notation and workshops
• The method promotes direct communication and reduces misunderstandings
• Domain storytelling can also be used for the development of test cases and code
• There are tools to support domain storytelling
• Domain storytelling is not suitable for all cases, but is one tool among many

Improved communication through domain storytelling

In this episode, I discuss domain storytelling, a method for improving communication between users and developers, with Henning Schwentner. Henning shares insights into his experiences and his book on the topic.

The basics of domain storytelling

Domain storytelling is more than just a method; it is a holistic approach to improving communication between subject matter experts and developers. By combining a workshop format with a graphical notation, it enables teams to visualize and better understand user requirements. This method addresses the essential point of understanding across the media divide - a challenge that arises in almost every software project.

The practice: How does domain storytelling work?

In our conversation with Henning, we dive into the practical implementation of domain storytelling. He divides the process into coarse- and fine-grained stories to highlight different aspects of a domain. From general overviews to detailed scenarios, each story helps to develop a deeper understanding of user requirements. These stories are then visualized through simple drawings using stick figures, symbols and arrows.

From diagram to code: The transformation

One particularly exciting aspect of domain storytelling is its ability to be seamlessly integrated into the development process. Henning describes how acceptance tests can be derived directly from the stories created. This close connection between professionalism and technical implementation not only promotes mutual understanding, but also accelerates the entire development process.

Tools and resources for successful domain storytelling

Henning shares a variety of resources and tools for using domain storytelling effectively. From physical whiteboards to specialized online tools, each method offers its own benefits. However, he particularly emphasizes the importance of direct communication between all stakeholders to realize the full potential of domain storytelling.

The role of domain storytelling in quality management

To conclude our discussion, it becomes clear how essential domain storytelling is for quality management in software development. By promoting understanding between all stakeholders and reducing misunderstandings, it makes a significant contribution to increasing product quality. Henning once again emphasizes the importance of an open approach to tools and methods - because not every method fits every situation.