# User story

In software development and product management, a user story is an informal, natural language description of features of a software system. They are written from the perspective of an end user or user of a system, and may be recorded on index cards, Post-it notes, or digitally in specific management software. Depending on the product, user stories may be written by different stakeholders like client, user, manager, or development team.
User stories are a type of boundary object. They facilitate sensemaking and communication; and may help software teams document their understanding of the system and its context.

## History

* 1997: Kent Beck introduces user stories at the Chrysler C3 project in Detroit.
* 1998: Alistair Cockburn visited the C3 project and coined the phrase "A user story is a promise for a conversation."
* 1999: Kent Beck published the first edition of the book Extreme Programming Explained, introducing Extreme Programming (XP), and the usage of user stories in the planning game.
* 2001: Ron Jeffries proposed a "Three Cs" formula for user story creation:
** The Card (or often a post-it note) is a tangible physical token to hold the concepts;
** The Conversation is between the stakeholders (customers, users, developers, testers, etc.). It is verbal and often supplemented by documentation;
** The Confirmation ensures that the objectives of the conversation have been reached.
* 2001: The XP team at Connextra in London devised the user story format and shared examples with others.
* 2004: Mike Cohn generalized the principles of user stories beyond the usage of cards in his book User Stories Applied: For Agile Software Development that is now considered the standard reference for the topic according to Martin Fowler. Cohn names Rachel Davies as the inventor of user stories. While Davies was a team member at Connextra she credits the team as a whole with the invention.
* 2014: After a first article in 2005 and a blog post in 2008, in 2014 Jeff Patton published the user-story mapping technique, which intends to improve with a systematic approach the identification of user stories and to structure the stories to give better visibility to their interdependence.

## Principle

User stories are written by or for users or customers to influence the functionality of the system being developed. In some teams, the product manager (or product owner in Scrum), is primarily responsible for formulating user stories and organizing them into a product backlog. In other teams, anyone can write a user story. User stories can be developed through discussion with stakeholders, based on personas or are simply made up.

### Common templates

User stories may follow one of several formats or templates.
The most common is the Connextra template, stated below. Mike Cohn suggested the "so that" clause is optional although still often helpful.
    As a <role> I can <capability>, so that <receive benefit>
Chris Matts suggested that "hunting the value" was the first step in successfully delivering software, and proposed this alternative:
    In order to <receive benefit> as a <role>, I can <goal/desire>
Another template based on the Five Ws specifies:
    As <who> <when> <where>, I want <what> because <why>
A template that's commonly used to improve security is called the "Evil User Story" or "Abuse User Story" and is used as a way to think like a hacker in order to consider scenarios that might occur in a cyber-attack. These stories are written from the perspective of an attacker attempting to compromise or damage the application, rather the typical personae found in a user story:
    As a disgruntled employee, I want to wipe out the user database to hurt the company

## Examples
### Screening quiz (epic story)

    As the HR manager, I want to create a screening quiz so that I can understand whether I want to send possible recruits to the functional manager.

### Quiz recall

    As a manager, I want to browse my existing quizzes so I can recall what I have in place and figure out if I can just reuse or update an existing quiz for the position I need now.

### Limited backup

    As a user, I can indicate folders not to back up so that my backup drive is not filled up with things I do not need to be saved.

## Usage

A central part of many agile development methodologies, such as in extreme programming's planning game, user stories describe what may be built in the software product. User stories are prioritized by the customer (or the product owner in Scrum) to indicate which are most important for the system and will be broken down into tasks and estimated by the developers. One way of estimating is by giving each task a number of story points selected from the Fibonacci sequence: 1, 2, 3, 5, 8, 13, with the simplest tasks given a score of 1 and more complex tasks given higher scores.
When user stories are about to be implemented, the developers should have the possibility to talk to the customer about it. The short stories may be difficult to interpret, may require some background knowledge or the requirements may have changed since the story was written.
User stories can be expanded to add detail based on these conversations. This can include notes, attachments and acceptance criteria.

### Acceptance criteria

Mike Cohn defines acceptance criteria as "notes about what the story must do in order for the product owner to accept it as complete." They define the boundaries of a user story and are used to confirm when a story is completed and working as intended.
The appropriate amount of information to be included in the acceptance criteria varies by team, program and project. Some may include 'predecessor criteria', "The user has already logged in and has already edited his information once". Some may write the acceptance criteria in typical agile format, Given-When-Then. Others may simply use bullet points taken from original requirements gathered from customers or stakeholders. In order for a story to be considered done or complete, all acceptance criteria must be met.

## Benefits

There is no good evidence that using user stories increases software success or developer productivity. However, user stories facilitate sensemaking without undue problem structuring, which is linked to success.

## Limitations

Limitations of user stories include:
* Scale-up problem: User stories written on small physical cards are hard to maintain, difficult to scale to large projects and troublesome for geographically distributed teams.
* Vague, informal and incomplete: User story cards are regarded as conversation starters. Being informal, they are open to many interpretations. Being brief, they do not state all of the details necessary to implement a feature. Stories are therefore inappropriate for reaching formal agreements or writing legal contracts.
* Lack of non-functional requirements: User stories rarely include performance or non-functional requirement details, so non-functional tests (e.g. response time) may be overlooked.
* Don't necessarily represent how technology has to be built: Since user stories are often written from the business perspective, once a technical team begins to implement, it may find that technical constraints require effort which may be broader than the scope of an individual story. Sometimes splitting stories into smaller ones can help resolve this. Other times, 'technical-only' stories are most appropriate. These 'technical-only' stories may be challenged by the business stakeholders as not delivering value that can be demonstrated to customers/stakeholders.

## Relationship to epics, themes and initiatives/programs

In many contexts, user stories are used and also summarized in groups for ontological, semantic and organizational reasons. Initiative is also referred to as Program in certain scaled agile frameworks. The different usages depend on the point-of-view, e.g. either looking from a user perspective as product owner in relation to features or a company perspective in relation to task organization.
While some suggest to use 'epic' and 'theme' as labels for any thinkable kind of grouping of user stories, organization management tends to use it for strong structuring and uniting work loads. For instance, Jira seems to use a hierarchically organized to-do-list, in which they named the first level of to-do-tasks 'user-story', the second level 'epics' (grouping of user stories) and the third level 'initiatives' (grouping of epics). However, initiatives are not always present in product management development and just add another level of granularity. In Jira, 'themes' exist (for tracking purposes) that allow to cross-relate and group items of different parts of the fixed hierarchy.
In this usage, Jira shifts the meaning of themes in an organization perspective: e.g how much time did we spent on developing theme "xyz". But another definition of themes is: a set of stories, epics, features etc for a user that forms a common semantic unit or goal. There is probably not a common definition because different approaches exist for different styles of product design and development. In this sense, some also suggest to not use any kind of hard groups and hierarchies.

### Theme

Multiple epics or many very large stories that are closely related are summarized as themes. A common explanation of epics is also: so much work that requires many sprints, or in scaled frameworks -- a Release Train or Solution Train.

### Initiative

Multiple themes, epics, or stories grouped together hierarchically.

### Epic

Multiple themes or stories grouped together by ontology and/or semantic relationship.

## Story map

A story map organises user stories according to a narrative flow that presents the big picture of the product. The technique was developed by Jeff Patton from 2005 to 2014 to address the risk of projects flooded with very detailed user stories that distract from realizing the product's main objectives.
User story mapping uses workshops with users to identify first the main business activities. Each of these main activities may involve several kind of users or personas.
The horizontal cross-cutting narrative line is then drawn by identifying the main tasks of the individual user involved in these business activities. The line is kept throughout the project. More detailed user stories are gathered and collected as usual with the user story practice. But each new user story is either inserted into the narrative flow or related vertically to a main tasks.
The horizontal axis corresponds to the coverage of the product objectives, and the vertical axis to the needs of the individual users.
In this way it becomes possible to describe even large systems without losing the big picture.
Story maps can easily provide a two-dimensional graphical visualization of the product backlog: At the top of the map are the headings under which stories are grouped, usually referred to as 'epics' (big coarse-grained user stories), 'themes' (collections of related user stories) or 'activities'. These are identified by orienting at the user’s workflow or "the order you'd explain the behavior of the system". Vertically, below the epics, the actual story cards are allocated and ordered by priority. The first horizontal row is a "walking skeleton" and below that represents increasing sophistication.

## User journey map

A user journey map intends to show the big picture but for a single user category. Its narrative line focuses on the chronology of phases and actions that a single user has to perform in order to achieve their objectives.
This allows to map the user experience beyond a set of user stories. Based on user feedback, the positive and negative emotions can be identified across the journey. Points of friction or unfulfilled needs can be identified on the map. This technique is used to improve the design of a product, allowing to engage users in participatory approaches.

## Comparing with use cases

A use case has been described as "a generalized description of a set of interactions between the system and one or more actors, where an actor is either a user or another system." While user stories and use cases have some similarities, there are several differences between them.
| | User Stories | Use Cases |
| Similarities | Generally formulated in users' everyday language. They should help the reader understand what the software should accomplish. | Written in users' everyday business language, to facilitate stakeholder communications. |
| Differences | Provide a small-scale and easy-to-use presentation of information, with little detail, thus remaining open to interpretation, through conversations with on-site customers. | Use cases organize requirements to form a narrative of how users relate to and use a system. Hence they focus on user goals and how interacting with a system satisfies the goals. Use case flows describe sequences of interactions, and may be worded in terms of a formal model. A use case is intended to provide sufficient detail for it to be understood on its own. |
| Template | As a <type of user>, I can <some goal> so that <some reason>. | Title: "goal the use case is trying to satisfy" Main Success Scenario: numbered list of steps Step: "a simple statement of the interaction between the actor and a system" Extensions: separately numbered lists, one per Extension Extension: "a condition that results in different interactions from .. the main success scenario". An extension from main step 3 is numbered 3a, etc. |
Kent Beck, Alistair Cockburn, Martin Fowler and others discussed this topic further on the c2.com wiki (the home of extreme programming).