Skip to content

Latest commit

 

History

History
32 lines (18 loc) · 1.32 KB

user-stories.md

File metadata and controls

32 lines (18 loc) · 1.32 KB

User Stories

What is it?

User stories are brief statements regarding the requirements of the system from an end-user perspective. It is often used in agile software development.

Why do you use it?

User stories are concise, easy to understand and are a great way to capture requirements. They can break down a project into smaller milestones that the team can work towards achieving.

When to use it?

This method is used early on in the process after the understand phase.

How to do it?

While the format varies on organizational/personal preferences, the traditional format for creating user stories uses the following statement:

As a (User Role), I (want/need) (goal/desire) so that (benefit).

Use of “need” versus “want” indicates if a requirement is required or a “nice to have” when building the system.

Example:

As a doctor, I need to get up to medical date records so that I know how to proceed with my patients’ treatment


References:

https://www.akendi.com/blog/scenarios-user-stories-and-use-casesoh-my/

https://www.interaction-design.org/literature/article/user-stories-capturing-the-user-s-perspective-quickly-and-simply

https://www.interaction-design.org/literature/article/user-stories-as-a-ux-designer-i-want-to-embrace-agile-so-that-i-can-make-my-projects-user-centered