Basic steps in identifying user stories when using a process approach:
- Define the business need (objective object reused on matrix model below)
- Define the top level process (BPMN collaboration used here) to define the workflow
- Harvested use cases directly from the top level model (no sub process decomposition yet) to associate user stories (A User Story is a brief statement of intent that describes something the system needs to do for the user) to 1st level use cases.
- This then is copied to the Matrix model to represent the KANBAN board (initial backlog, itterations & user stories according the sprint phases).
This approach is simple and practical, your views please?