This template is to describe the user story for a desired feature. It intends to explain the user role in a system, the desired activity, and what is intended to be accomplished by successfully completing the user story. For our Agile dev team, user stories are the primary method of understanding user needs, so they can build it right.
...
...
As a < type of user >, I want < some goal > so that < some reason >.
When < situation> I want to < Motivation > so that < Expected outcome >.
...
###Acceptance criteria Specify the requirement(s) by which the user story can be accepted as completed correctly and meet the user need. List the goal and metrics to judge its success.
Goal: (e.g., Simplify the user experience) Metric: (e.g., Customer Satisfaction score increases)
...
Links to any documentation should be included on the card, or attached to the card, and checklists can be created to track the tasks or user stories to build the feature.