Story Mapping practice
Jeff Patton proposed a communication practice that lets you discover and structure user requirements, trace them to business goals and to the specific people who perform an activity in order to achieve those goals (Personas method). For story mapping you need a horizontal surface (tables) or a vertical surface (a wall) on which you can stick colorful sticky notes.
Together with the business user or the customer's representative, you identify personas, who need automation. For each persona you record goals, for which development or enhancement of the software system is planned. Goals are written on yellow sticky notes. Business activities that personas perform in order to achieve the goals are written on blue sticky notes placed under the corresponding goals. Under each activity, specific actions of the user in the system are written on yellow sticky notes (usually such actions are recorded in the User Story format).
An example of how this can look:
This is an important artifact that the customer and the Assignee use to track implementation progress. It cannot be left on the wall or on the table in that form, because the sticky notes will simply fall off, or someone will accidentally take them down and throw them away. The map must be digitized, and the Features module (or Epics) is an excellent fit.
First configure the reference list of function levels and add the values Persona, Goal, and Activity. After that you can record the story map as follows:
