How to write a User Story

User Story is an informal, natural language description of Features of a software system. User Stories are written from the perspective of an end user of a system.

The Why / Reason behind the Feature

The most important part of writing a User Story is to know about the Why. Knowing the "Why" helps everyone in the team to be more productive.

Writing a descriptive Subject

Story Subject is the first thing the Owner sees. Make sure the subject provides an understandable Big Picture of what needs to be done and why.

As a <role> I want to be able to <goal / need> so that <why>

A Scenario for all Seasons! ;)

Not only the Owner should understand the Scenario but also all members that are involved in MG's Development Cycle of a Feature.  

You can pick the following lines:

The more clear, the faster to develop!

Do not underestimate the power of "Important Notes" when writing a User Story. Important Notes can be written underneath the Scenario.

Evidence that can help?

Attach useful evidence as much as possible. Don't leave other members, with a bare screenshot, Instead use highlighting/drawing tools to define where you want to point in screenshots.

An example of a User Story:

As a User I want to be able to login so that I access the dashboard

1. Given: Please enter your username
2. Given: Please enter your password
3. When: I enter my username
   1. Input Type Email
4. And: I enter my password
   1. Input Type Password
5. Then: I click on Login button
   1. Only one click at a request cycle possible
6. When: Username & Password match
   1. If not match, See the note
7. Given: You have successfully logged in
   1. Show in a green success popup
8. Then: I am redirected to the dashboard page

Important Note:

Username & Password doesn't match? Show a proper meaningful message in a popup