User story

user storiesstoriescustomer's story languagedevelopment goalsepics
In software development and product management, a user story is an informal, natural language description of one or more features of a software system.wikipedia
54 Related Articles

Requirement

requirementscustomer requirementcustomer needs
User stories are often confused with system requirements.
Example: 'The contractor must deliver the product no later than xyz date.' Other methods include use cases and user stories.

Fibonacci scale (agile)

Fibonacci scalerounded Fibonacci scale
One way of estimating is via a Fibonacci scale.
In Agile software development, the Fibonacci scale consists of a sequence of numbers used for estimating the relative size of user stories in points.

Extreme programming practices

planning gameSmall releases
With Extreme Programming (XP), user stories were a part of the planning game.

Extreme programming

XPcollective code ownershipcourage in programming
With Extreme Programming (XP), user stories were a part of the planning game. Kent Beck, Alistair Cockburn, Martin Fowler and others discussed this topic further on the c2.com wiki (the home of extreme programming).
A customer is able to test the system periodically according to the functional requirements, known as user stories.

Scrum (software development)

Scrumproduct ownerproduct backlog
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.
The product owner defines the product in customer-centric terms (typically user stories), adds them to the product backlog, and prioritizes them based on importance and dependencies.

Use case

use casesuse-caseUse case diagram
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."
Brief: (equivalent to a user story or an epic)

Software development

developmentdevelopedapplication development
In software development and product management, a user story is an informal, natural language description of one or more features of a software system.

Product management

ProductProduct portfolio managementproduct portfolio
In software development and product management, a user story is an informal, natural language description of one or more features of a software system.

User (computing)

userusernameusers
User stories are often written from the perspective of an end user or user of a system.

Post-it Note

post-itPost-it notessticky note
They are often recorded on index cards, on Post-it notes, or in project management software.

Boundary object

boundary objects
User stories are a type of boundary object.

Sensemaking

sense-makingmade sense ofretrospective narrative
They facilitate sensemaking and communication; that is, they help software teams organize their understanding of the system and its context.

Alistair Cockburn

Cockburn, Alistair
In 1998 Alistair Cockburn visited the Chrysler C3 project in Detroit and coined the phrase "A user story is a promise for a conversation." Kent Beck, Alistair Cockburn, Martin Fowler and others discussed this topic further on the c2.com wiki (the home of extreme programming).

Mike Cohn

In 2004, Mike Cohn generalises the user story principles beyond the usage of cards in a book that is now considered as the reference standard for the topic according to Martin Fowler.

Martin Fowler (software engineer)

Martin FowlerFowler, Martin
In 2004, Mike Cohn generalises the user story principles beyond the usage of cards in a book that is now considered as the reference standard for the topic according to Martin Fowler. Kent Beck, Alistair Cockburn, Martin Fowler and others discussed this topic further on the c2.com wiki (the home of extreme programming).

Persona (user experience)

personasPersonamarketing persona
User stories can be developed through discussion with stakeholders, based on personas or simply made up.

Five Ws

Circumstances5 WCircumstances (rhetoric)
Another template based on the Five Ws specifies:

Jira (software)

JIRAAtlassian JIRAJira BugTracker
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 ).

Hierarchy

hierarchicalsubordinatehierarchies
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 ).

Time management

task listto-do listtime-management
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 ).

Kent Beck

Kent Beck, Alistair Cockburn, Martin Fowler and others discussed this topic further on the c2.com wiki (the home of extreme programming).

Experience architecture

Experience architecture (XA) is the art of articulating a clear user story/journey through an information architecture, interaction design and experience design that an end user navigates across products and services offered by the client or as intended by the designer.