projectdoc Toolbox

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.

ID: user-story
Suite: Agile Team
Parent: Doctypes for Agile Planning
Documentation Type: Q2 - Project
Categories: / Work / Unit
Tags: Agile Planning

Properties

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.

Type

The type of the story. Valid types are

Type	Description
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.

Theme

Stories may be grouped by features.

Actor

The list of user characters that take part in the user story.

Goal

The goal pursuit by the user.

Business Value

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.

Relevance

The following values are valid:

Value	Description
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.

Business Priority

The priority of the story from a business point of view.

Technical Priority

The priority of the story from a technical point of view.

Story Points

The relative size of the story.

Status

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:

Value	Description
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.

Reference

Add references to information on external systems here.

Sections

Description

A usually formal description of the user story.

Business Goals

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.

Test

The test to check, if the story has been implemented successfully. May contain more than one test.

Tasks

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.

Notes

These are internal notes that are usually not exported and only visible to team members with write access.

But this is not a safe place to store sensible information. It is just a convenience for the reader to not be bothered with notes stored here for the authors for later use. The security level is about suppressing the representation by a CSS style. Therefore consider this as a convenience for the reader, not as a security tool.

The text of notes sections is also indexed.

References

For a document the references section contains pointers to resources that prove the statements of the document.

Often these proofs are not easily distinguishable from further information. In this case you may want to skip the reference section in favour for the resource list.

For further information please refer to References and Resources.

Resources

The resources section provides references to further information to the topic of the document.

This may be information on the internet provided by the resource or information in the team's information systems. Anything the reader of the resource might want to know, may be listed here.

For further information please refer to References and Resources.

Related Doctypes

User Character

User characters are the actors of user stories.

Feature

User stories may be grouped into theme by features.

Space shortcuts

Page tree

Docs

Support

Free Blueprints

Tooling for Blueprints

Free Extensions

Spaces

Plugins for Maven

Incubator

Libraries for Java