User Stories

Agile User StoriesUser Stories are a simple way of capturing user requirements throughout a project – an alternative to writing lengthy requirements specifications all up-front.

User Stories are derived from XP (Extreme Programming), however they can just as easily be used for requirements gathering in any agile development methodology, or indeed in any home-grown development process.

A User Story is a simple statement about what a user wants to do with a feature of the software, written from a user’s perspective. A User Story should not use technical jargon or state design goals. User Stories should be written in business language that is understandable to all.

A User Story should focus on the who, what and why of a feature, not how.

For example, on a job site, two high-level User Stories might be:

  • As a job seeker, I want to search for a job, so I can advance my career.
  • As a recruiter, I want to post a job vacancy, so I can find a new team member.

This is a useful construct to give a consistent shape to User Stories, and to act as a constant reminder to focus on who, what and why:

As a [user role], I want to [goal], so I can [reason].

Some people may consider the third part of the construct to be unnecessary. However I think it’s good to state the user’s motivation for using the feature, because:

(a) it gives clarity as to why a feauture is useful;
(b) it can influence how a feature should function;
(c) it can give you ideas for other useful features that support the user’s goals.

At the start of a project, capture an initial list of User Stories up-front. In Scrum this would be the initial Product Backlog. This feature list is useful for estimating and planning. But defer capturing all the details until the story is prioritised and due to be developed in the next Sprint or iteration.

In meetings with users (or user representatives), users will often tell stories about the failings of their current system or process. Or they might tell stories about how they see things working better in future. Try capturing these stories as User Stories. On cards. While you’re in the meeting. As they are told.

In traditional development projects, these stories often aren’t captured as they are told, they’re captured in a lengthy analysis process and captured in a lengthy document; a format that isn’t particularly user friendly.

Using User Stories, you might be surprised just how easy it is to leave a meeting with users, with their key requirements already captured.


11 Responses to “User Stories”

  1. Oleg Puzanov says:

    I would like to use nine boxes tool for user stories building. More can be read here:
    and here in russian:

  2. Andrew Orange says:

    It can also be useful to keep pushing the “so that”s to achieve a hierarchy of aims. c.f. Coverdale. Sometimes these can completely change one’s perspective on the task in hand.

    E.g. as a user I want to receive email alerts of new jobs SO THAT I don’t have to keep back in the site for new jobs SO THAT I can save time job seeking. AND SO that I am first to know about jobs as soon as they are posted… SO THAT

    … which could lead one to other, more effective solutions – e.g. RSS

  3. AgileJoe says:

    I also like to include the detriment as you can assess value during the planning game with the customer.

    [As as][I want][So that:Benefit] [If I don’t:detriment]

  4. Nash says:

    Stories sounds like a key concept but your example doesn’t sound helpful at all for estimating.

    You said: As a job seeker, I want to search for a job, so I can advance my career.

    Now search can be as simple as simple text search.

    It could be more complicated with say with filters on experience required, skill required, location.

    It could have sorting on the results; sorting could be on any one of 10 possible job attributes.

    With such a wide variation of the simple “As a job seeker, I want to search for a job, so I can advance my career.” How can that be useful to generate an estimate?

    I think it is useful for the customer to speak as much as they like about the story. It wouldn’t hurt if they said: “As a job seeker, I want to search for a job, so I can advance my career. I should be able to search by location, by skill, by experience, by salary, by keywords. All the results must fullfill all my criteria.”

    Wouldn’t that be more useful?

  5. hssaroch says:

    Epic is the solution to the problem that you have mentioned. An epic is like a user story but on a very high level. Many user stories may fall under one epic.

  6. Nash says:

    Thank you Hssaroch! I will look into Epics for sure. I’d love to know if you have a handy link.

  7. Tarek Koudsi says:

    Been using User Stories for a while and almost always get confused, only now I know they call it “Epic”..

  8. Excellent definition of the User Story.

  9. Erman Taylan says:

    Hi Kelly,

    Really useful article. And i have a questions for you:

    Is there any approach between test cases and user stories. Like, “for one user stories, create one tc” or something? Or it depends on what user stories’ scope?



  10. Anuradha says:

    Who owns and write the user stories?

Leave a Reply

What is 3 + 8 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)