User Stories document a requirement of a stakeholder with a specific business goal. It also provides an acceptance test. It is a representation of a unit of work.
The document type user story provides the following properties:
Please note that only information about specific properties is provided here. Common document property used by all document types are documented by Document Properties.
The type of the story. Valid types are
|story||A typical user story.|
|epic||A larger story to be broken into smaller before it can be estimated|
|constraint||A constraint card.|
|spike||A spike to explore an unknown terrain.|
|defect||A bug to be resolved.|
Stories may be grouped by features.
The list of user characters that take part in the user story.
The goal pursuit by the user.
The business value realized by accomplishing the goal.
Frequency of Use
The expected frequency of use. Dependent on the product this may be numbers like 'uses per visit/task/... of one user', 'uses per hour/day/week/month of one/all user(s)'. It is not important to compare two user stories by their frequency, it is important for the developer to get to know how often the function will be used by users of the system.
The following values are valid:
|must have||The story is about something users regard as must-have of the product.|
|linear||The story is about something users regard as the-more-the-better.|
|exciter / delighter||The story is something that excites or delights users.|
|enhancement||The story is about a minor enhancement.|
The priority of the story from a business point of view.
The priority of the story from a technical point of view.
The relative size of the story.
The status of the user story in a coarse granular sense. This status value is not used to actively track the status of a user story (this task is shifted to the task tracking or issue management system), but to mark it as being active and to be done or discarded. The status of the user story may take one of these values:
|proposed||The user story has been proposed, but has not yet been accepted or rejected.|
|active||The user story is in the state of being worked on.|
|done||The user story has been completed.|
|discarded||The user story has been rejected and now is discarded.|
Add references to information on external systems here.
A usually formal description of the user story.
In case more space is needed to add information about the business goals of the story. Usually everything is said in the description of the story.
The test to check, if the story has been implemented successfully. May contain more than one test.
A short description of the identified tasks associated with the story. This is just a short note and may link to other resources with detailed information.
Usually tasks are tracked with the issue management system alone.
Subordinate User Stories
Split stories and organize them hierarchically by adding User Story documents as child pages.
User characters are the actors of user stories.
User stories may be grouped into theme by features.