User story

A user story is a short, simple description of a feature told from the perspective of the person who desires the new functionality. User stories are one of the main agile development techniques. A typical user story describes who wants what and why.

User stories are used throughout agile software development to capture high-level requirements. They are written from the point of view of the person who desires the new functionality, not the developer. They are usually brief and to the point.

The following tips will help you write effective user stories:

1. Describe the problem that needs to be solved, not the solution.
2. Use “I want” or “I need” statements to articulate the user need.
3. Be specific about what the user wants, but don’t get too bogged down in the details.
4. Keep the story focused on a single functionality.
5. Prioritize user stories and determine what can be implemented in the next release.

‍

What is the purpose of a user story?

The purpose of a user story is to provide developers with an understanding of what needs to be built and why it needs to be built. It also helps stakeholders understand how their requirements will be implemented in the final product.  

How do you write a good user story?  

A good user story should include three key elements:

1) Who wants this feature;

2) What they want;

3) Why they want it.

Additionally, it should be written in language that everyone can understand and use active verbs to describe desired behavior.

Fun Fact:

"User stories have been found to be effective in helping teams build better products, as demonstrated by a study from the University of Limerick which found that teams using user stories were more successful in meeting customer requirements than those who did not." (McCarthy et al., 2017)

‍