User Story

Document Properties Marker

override	false

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

Doctype doctype hide

Name User Story

ID user-story

Set Agile Team

Parent

Parent Property

parent-doctype	topic
property-name	Name

Audience

Name List

doctype	role
render-no-hits-as-blank	true
property	Audience

Documentation Type

Name List

doctype	doctype-type
render-no-hits-as-blank	true
names	Q2 - Project
property	Documentation Type

Tags

Tag List

names	Agile Planning

Iteration


value	focused

hide

Sort Key hide

Section

index	true
title	Description

Section

title	Properties

Transclusion

document	Note Box referencing common Document Properties
ids	Box

Section

level	2
title	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.

Section

level	2
title	Theme

Stories may be grouped by features.

Section

level	2
title	Actor

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

Section

level	2
title	Goal

The goal pursuit by the user.

Section

level	2
title	Business Value

The business value realized by accomplishing the goal.

Section

level	2
title	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.

Section

level	2
title	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.

Section

level	2
title	Business Priority

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

Section

level	2
title	Technical Priority

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

Section

level	2
title	Story Points

The relative size of the story.

Section

level	2
title	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.

Section

level	2
title	Reference

Add references to information on external systems here.

...

Section

title	References

Section

title	Resources

Piwik Set Multiple Custom Variables

Name	Value
Department	projectdoc
Category	projectdoc-doctype
Type	agile

Space shortcuts

Page tree

Docs

Support

Free Blueprints

Tooling for Blueprints

Free Extensions

Spaces

Plugins for Maven

Incubator

Libraries for Java

Incubator

Add-ons for Confluence

Tools

Support

Team

Legal

Versions Compared

Old Version 3

New Version 4

Key

About

Keep up-to-date!

Powered by