Basic architecture work is not difficult, but it is often neglected. If the architectural goals are not clear, the decisions made will not necessarily match the specified framework conditions and necessary quality requirements and, in the worst case, may even cause the project to fail. The specialist department and the role of the product owner primarily focus on the technical requirements, so there are initially no specific architecture tasks in the product backlog.

Quality scenarios help us to make architecture work visible and thus plan it into the iterative, incremental way of working. We can also use scenarios to qualitatively evaluate our software architecture. In this presentation, we will look at what types of scenarios there are, how you can create them or keep them up to date, and how you can benefit from them in your daily work.