Domain Storytelling

Technical requirements in software development: Understanding and being understood

Finding technically motivated boundaries in domains in order to organise software and teams accordingly
Deriving requirements from domain stories
Combine domain storytelling with event storming, user story mapping and other methods of agile software development

Storytelling is deeply rooted in human communication - this also applies in the age of software. Telling and visualising "specialist stories" makes business processes and specialist knowledge tangible.
This book shows how you can develop technically coherent application software using simple means. Domain storytelling helps to transport specialist knowledge from the minds of users to the minds of developers, product owners, product management and business analysts. It brings those involved together in workshops to agree on tasks and processes within the company. The result is documented in a simple visual language.
Stefan Hofer and Henning Schwentner use clear examples to explain how domain stories are created and how domain storytelling can be used for domain-driven design, requirements elicitation and other purposes.