Finally also in German
Technical requirements in software development: understanding and being understood.
- Find subject-motivated boundaries in domains to organise software and teams accordingly.
- Derive requirements from domain stories
- Combine domain storytelling with event storming, user story mapping and other agile software development methods.
Storytelling is a fundamental form of human communication - also in software development.
Domain experts and development teams make expertise tangible by telling and visualising business processes as technical stories. Domain storytelling enables all participants to understand the relevant roles, tasks and work items.
Stefan Hofer and Henning Schwentner introduce a visual language as a graphic notation and explain scenario-based modelling, the workshop format and the combination with other modelling methods. Using case studies, they show how domain storytelling solves common problems:
- Aligning all stakeholders and affected parties from IT and business departments.
- Modelling workflows in a comprehensible way with simple symbols and rules
- Find better solutions faster with collaborative modelling workshops
- Find good and clear boundaries to organise software and teams accordingly
- Turn expertise into requirements in an agile process
- Develop implementable domain models
- Get a better overview of an IT landscape to consolidate or optimise it
In this book you will find instructions and helpful tips on how to better understand your business processes, improve communication with your (IT) colleagues and combine your approach with other methods of agile software development.