User Stories. How can I use it? How can I eat it?

On this topic we're gone to talk about what is and how to make good "User Stories". First at all, user stories are a tool that can be used for the practice known as "Scrum" , which is used for teams of development on projects. It consist of make some questions about the purpose of the application and requirements also needs of the customer.

The user story is a structure is an scenario of the requirements of the application, so it used this basic structure:

As a <person>

I want <what>

so that <why>

Let's try an scenario when we need to sign up for any application, fill in the boxes of a form. So we need to digit our personal data.

 As a

This is the subject of the user story, so we could say this, as example:

• As a sign up user.
• As a administrator.
• As a regular user. 

I want

In this step of the structure we say our need, so we want to express our vision of the results of the application, for example:

• As a sign up user --> I want to fill the form of my personal data correctly.
• As a administrator --> I want to check the request of the new and regular users.
• As a regular user --> I want to access and view correctly my home page.

So, we could see how we want a result for our user, and this user need some result for his actions. At this part we only need the <so that> part.

So that

The third part represent the result of the action of the person (our user). It's the acceptance scenario of our request as user. For example:

• As a sign up user --> I want to fill the form of my personal data correctly --> So that confirm me as a regular and new user, so I can access the features of the page.
• As a administrator --> I want to check the request of the new and regular users --> So that give me rights for accept the new people and respond the doubts of the regular users.
• As a regular user --> I want to access and view correctly my home page --> so that allow me to interact with other users and bring me rights for contribute with the page making new posts.

As we see, the user stories help us for make great requirements for the applications. This is a usual practice on the develop software teams, this practice reduce the time of thinking on the needs of the customer and help us for make better code.

Like always, this is my understanding of what is the user stories, I could be making a mistake of the description of the situation. On the next topic we are gone to talk about the acceptance criteria of the user stories, this practice give us a plus and help us to understand better the user stories.

References

For made this topic I used as reference the post of 10 Tips for Writing Good User Stories. I hope they don't demand me.