A user story is used to define product or system functionality and the associated benefit of the functionality. In an Agile environment, projects are commonly comprised of a large number of user stories representing various levels of system/product user. This ever growing and prioritized list of user stories is called as product backlog. The user story describes the type of system/product user, what functionality they want, and why they want it. The format of a user story should be:
As a <type of user>, I want to <feature/function> so that <reason/value>
As a <type of user>, I want to <feature/function> so that <reason/value>
