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:

In a SAP Project perspective, we can redraw it as follows:

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:

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:

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...