While I consider the so-that clause optional, I really like this template. In my user stories book and in all my training and conference sessions on user stories I advocate writing user stories in the form of: "As a , I want so that ." Een user story is een korte beschrijving (story) van wat een gebruiker (user) wil. Title: Story-----As a , I want , so that I can . Your user stories should include enough information for your product manager to decide how important the story is. User stories are often written from the perspective of an end user or user of a system.They are often recorded on index cards, on Post-it notes, or digitally in project management software Depending on the project, user ⦠For example, choose User Story to view templates defined to capture user stories. If you want to describe the entire workflow or interaction, however, I recommend using a scenario, storyboard, or story map, see my post Agile Scenarios ⦠There is a common pattern of how to write a user story, which is: As a particular type of a user I want to do something so that some reason. It is essentially a development of the user story, and ⦠Or to generalize, like this: ... Long story ⦠A UX storyboard shows their embeddedness in daily situations, as well as the scenarios where people use them. Feature) User story - a small story that describes a particular feature. A user story in Agile represents a refined form of some customer requirement. They typically follow a simple template: As a type of user >, I want some goal > so that some reason >.. A user story is a short (a sentence or two), simple, and specific description of an interaction with an in-development product, usually an app or website. Acceptance Criteria-----Scenario A: Given that , when , then