Story mapping for SAP projects
Story mapping is a top-down approach to requirement gathering. It arranges user stories into a useful model that is easy to understand and allows you tell your user story in a simpler way. It helps you identify missing details (if any) in your backlog and effectively plan the release.
In general, the story map structure looks as follows:
![](https://static.packt-cdn.com/products/9781788470360/graphics/40929a3d-41b9-47ad-820d-e90a80c0d7bd.jpg)
In a SAP Project perspective, we can redraw it as follows:
![](https://static.packt-cdn.com/products/9781788470360/graphics/af8ad75b-6f12-438a-962d-d5e1f8c5bfe9.jpg)
Now, let's see how the structure of a story flows. As depicted in the following image, we start with Epic Business Context (scenario) and break it down further into processes and process steps:
![](https://static.packt-cdn.com/products/9781788470360/graphics/1e69b7c2-4bf6-419a-bf5e-0f105b5ffcbb.png)
Story map structure flow in a SAP context
For example, plan to produce -> demand management -> forecast product demand.
Let's see what a user story looks like in a scrum model and in a SAP Project:
![](https://static.packt-cdn.com/products/9781788470360/graphics/e9a6b234-115b-441e-b940-cb3aebdede97.png)
User story format
Non-functional requirements
A common challenge while writing a user story is how to handle a product's non-functional requirements. These are requirements that are not...