User-Story

A user story ( " user story" ) is one formulated in everyday language software requirement. It is deliberately kept short and usually includes no more than two sentences.

User stories are in the context of agile software development (eg Extreme Programming (XP), Scrum ) is used together with acceptance tests for the specification of requirements. Each user story is written on a story card. The author of the story should be the customer of the software project. The User Story is the most important method to control an agile project.

Create user stories

User stories can be placed either informally or using a template:

"When I want to " Subsequently, the shortest one:

"When I want " Examples

The following two examples show the structure of each of a heading and a single sentence.

The following example, however, uses the template "When I want to ":

Story Decomposition

Story Decomposition ensures that the user stories are described in an adequate level of detail, and that the user stories are derived from the user goals. The procedure is the width in depth to refine the requirements gradually: starting point is to reach user goals; Epics are derived from it, which are broken down into user stories; the user stories are supplemented with acceptance criteria.

Story Map

A Story Map showing user stories in a graphical overview. Horizontal successive activities of the user are each represented with a user story. Vertical is detailed from top to bottom: eg starting with the customers targets over Epic's up to the user stories. Through a Story Map is an overview of all user stories is made.

Demarcation User Story to Use Case

The use cases in the traditional software development, agile methods are not user stories similar in that they represent requirements in the language of the user and the context.

In a use case, however, all success and failure scenarios to be pooled in the possible achievement of a professionally relevant objective. A user story, however, is a professionally motivated requirement is that it can be assessed by a user while as successful or not implemented successfully, but the user is not able to achieve professional goal solely with the user story.

Thus, the context for many user stories form a Use Case: A user story is the title of a concrete scenario, a use case contains several of these scenarios.