Agile mythology follows lean documentation it doesn’t mean there is no documentation takes place. In Agile user story is main the document to narrate user requirement in simple fashion. User stories are basically used in agile software development. User stories are basically description of a software feature from an end user perspective. A user story describes the type of user, what they want and why.
A User stories template uses the following types of format.
So in simple words you can say it cater following elements.
- Who it is for?
- What it expects from the system?
- Why it is important (optional?)?
Role – The user should be someone who interacts with the system.
Feature – As name suggest it should be the list of features that use want to do. Behavior of the system should be written as action.
- Usually unique for each user stories
- Active voice should be used instead of passive voice(“Can be notified”)
Reason – As name suggest, you need to write as a user why you want this feature. In other word what benefit a use will have with this feature.
- Many user stories can share same reason or benefits.
Example of User stories –
- As a [customer], I want [shopping cart feature] so that [I can purchase items online].
- As a [customer], I want [to be able to view the items in my cart] so that [I know for sure what I’m purchasing].
An agile story should be short, so that it can be fit in the sticky note or note card. User stories should be written in business language so that it can be easily understandable to business people as well as scrum team what customer wants and why they need particular feature.