Owners of the product have special requirements related to how the Product should include users in the complex workflow of the business process (approval and what is not). The easiest way to document this requirement is through a process diagram / flowchart.
Scrum, however, recommends that the requirements be in the form of user stories. What is the best way to approach this?
Option 1
Have common user stories that span the workflow and attach the flowchart diagram as a supporting document. For example, as an author, I want to be able to submit my article for approval so that it is published.
Pros
make it easier for people to understand and digest, rather than reading 10-20 user stories.
against
he becomes epic
Option 2 Break the complex flowchart into your own user stories. For example, As an author, I want to submit my article. As an editor, I would like to be notified when an article has been submitted so that I can review it. As an editor, I need to approve the article. As an editor, I would like to be able to request additional information ...
Pros
Pure Scrum. easy to prioritize / rate / plan
against
As you can see, even a short business process workflow will easily explode in many user stories.
source
share