User Story

...

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 relevance of the story to get a deeper understanding of its emotional value.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	Sections

Section

level	2
title	Description

A usually formal description of the user story.

Section

title	Summary

Transclusion

document	Summary
ids	Designation

Section

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

Section

level	2
title	Test

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

Section

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

Section

level	2
title	Subordinate User Stories

Split stories and organize them hierarchically by adding User Story documents as child pages.

Transclusion

document	Document PropertiesSections
ids	standard-sections-bottom

...

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 1

New Version 2

Key

About

Keep up-to-date!

Powered by