User stories

User stories are simplified description of a small chunk of requirement or business functionality within a feature from the perspective of the user or customer.

What is User stories

User stories are simplified description of a small chunk of requirement or business functionality within a feature from the perspective of the user or customer. User stories are the items in the product backlog, and each item comprises about 1-3 days or 40 hours of work. User stories written on index cards or sticky notes. User stories common format is as follows:
  • As a (role/persona) I want (feature/some goal/etc) so that (reason/value/benefit)
  The common format for acceptance criteria of each user stories is.
  • Given (a pre-condition) When (the user does some action) Then (the outcome of the action)

Top related courses to User stories

Related methods and techniques to User stories

  • Three C’s Of User Stories (Card, Conversation and Confirmation)

    1. Three C’s Of User Stories (Card, Conversation and Confirmation)

    The 3 C's (Card, Conversation and Confirmation) are the 3 critical aspects of user stories:


    Card: just enough text to identify the story
    Conversation: the details of the stories are communicated in discussions between the customer and the development team.
    Confirmation: Cards also include customer's acceptance criteria – the tests that can be used to confirm if the user stories are implemented correctly.

  • Hierarchy of Epics, Features, Themes and User stories

    2. Hierarchy of Epics, Features, Themes and User stories

    Project requirements or project work can breakdown as follows:

    • Epic: large user stories that span several iterations.
    • Features: attributes of the product (a high-level business functionality)
    • Themes: a number of related user stories that are grouped together to speed up the estimation
    • User Stories: decomposition of features
    • Tasks: the smallest element of decomposition
  • INVEST attributes of User Stories

    3. INVEST attributes of User Stories

    INVEST is the acronym for six attributes of a good user story:

    • Independent: stories can be prioritized in any order
    • Negotiable: User stories can be discussed with the product owner and tradeoffs made based on functionality and cost.
    • Valuable: user stories must have a clear value
    • Estimable: user stories can be estimated for the amount of work they require
    • Small: small user stories (4 to 40 hours of work) are easier to create and test than large user stories;
    • Testable: the outcome of the story must be testable