Project Management Tool - The Power of Agile Teams
  • 8.200+ business use to manage their agile projects
Sign in - It's free!

# What is it and how does it work?

The User Story is a way to define software requirements. Your goal is to define a requirement in a non-technical way and from the viewpoint of a user, so that any person who comes into contact with it can easily understand what the need, that is, the specified requirement is.

# Understanding the best practices

The user Stories must clearly explain for whom, what, and what is the reason for something to be developed. A definition of requirements in projects that follow the scrum framework, that is, based on the User Story, must contain these three elements. That way, you can see that a User Story is efficient due to the way it is defined. The user stories are usually written in the same format: As a , I would like to , so that .

Good user Stories usually meet a list of requirements that are known by the acronym INVEST.


I - Independent: A good User Story must be independent, that is, its execution must not be related to the execution of another User Story so that it doesn’t reflect on complexity at the time of prioritizing and estimating your efforts.
N - Negotiable: The definition of requirements through the User Story on scrum works as a great box of possibilities for the project, that must be easy to interpret and have a clear goal. However, they are not very detailed. They must be detailed before the beginning of a Sprint. Therefore, the User Stories must be negotiable, that is, they must enable the team to debate about solutions for the execution of your requirement.
V – Value Added: The User Stories must necessarily add value to the user. Therefore, you shouldn’t write a Story for no reason. By creating a new Story, the people involved must be certain of the added value it will bring to the deliverable.
E - Estimable: Every work in project management bust be possible to estimate, or else a project is fated to the unknown. That way, it wouldn’t be any different with a User Story. The scrum team must have the possibility of estimating the work and complexity for its development.
S - Small: Good User Stories must be small, they must contemplate a small fraction of the scope, in a way that they can be easily allocated in the sprints. When a User Story is defined in a way that it is not inserted in a sprint for being too large, it becomes “epic” and must later be fragmented.
T - Testable: A good user story must add value to the user, and therefore, the work developed can be submitted to trials to validate the added value, as well as the compliance with the scope.

# How to create a User Story

To create a User Story on GitScrum, you have to, from the access to your project, click on “Project Options” (Step 01 on the image below) and then select the option “Create User Story” (Step 02).

At this moment, you must register your new User Story by filling out a small form with your data.

A - Priority: In this field, you must inform the priority that was identified for this new User Story that is being created. At the end of this material you can check how to manage your priority list;
B - User Story: In this field, you must fill your user story. Remember that it is strongly recommended that it is written following the standard: As a , I would like to , so that ;
C - Additional Information: In this field, you must add additional information that is relevant to the user story;
D - Acceptance Criteria: In this field, you must fill the acceptance criteria that were defined for this user story. (In the section “Understanding the best practices” you can better understand how to define these criteria;

# How to edit the User Story Priorities

To edit a User Story that has been registered on GitScrum, you have to, from your project, click on the “User Stories” option on the left side menu, as shown in step 01 on the image below. Right after, you must click on the User Story options menu that you wish to edit (Step 02) and finally, select the “Edit User Story” option shown by step 03 on the image.

At this moment, you are directed to the update page of your User Story, where you can change any information at any moment. Then, you must click on the “Confirm” button so that your changes are saved.

# How to assign tasks to a User Story

The task assignment for a User Story is very simple. You can perform this procedure through the window of a task selecting the “User Story” field as shown in the image below.

When you need to link many activities to a User Story, you can perform this assignment in a simpler and quicker way. For that, you must access a certain project and then select, on the left side menu, the “User Stories” option (Step 01 on the image below). A list with your User Stories will be shown, and at this moment, you must open the options menu (Step 02) and select “Assign Tasks” (Step 03).

At this moment, you will have a list of your project’s tasks. On the first column, (highlighted below), the list will show options to assign a task to the current User Story, and in this case, you must click on the “Add to this User Story” button. You can also remove tasks by clicking the “Remove from this User Story” button, and finally, you can remove tasks from another User Story and simultaneously assign it to your current User Story by clicking on the “Switch to this User Story” button.