Creating User Stories

You start this process by writing the “title” of the specific user story. This title follows a very specific format:

As a/an [user type] I want [feature] so I [benefit]

In order to generate the required number of user stories to best describe your requested capability, you can add as many User Story Titles and Conditions of Acceptance as you need to by clicking on the + (plus) sign below the “Conditions of Acceptance” field on this form.

Examples of user story titles can be:

  • As an author I want a spell checker so I can avoid spelling errors in my documents
  • As a shopper I want a wishlist so I can remind myself of things I’d like to buy in the future
  • As a salesperson I want a sales forecast report so I can ensure I’m on track to hit my quota

Example of a User Story “Conditions of Acceptance” entry:

For the purposes of this example, we’ll use the example of the “spell checker” story (the first one of the user story title examples). The following list of conditions would need to be met for the benefits of the story title to be satisfied.

Conditions of Acceptance example:

  • I can check spelling for my entire document
  • I can step through each spelling error one at a time
  • I can see suggestions
  • I can replace my word with a corrected word
  • I can add words to my dictionary
  • I can check spelling in English


User Stories

A user story is a description of a feature that is very lightweight, easy to understand, and quick to write. One of the key benefits is the ability to describe the vision of the project to the whole team, without spending weeks creating detailed requirements.
  • Please enter the name of your company
  • User Story Titles & Conditions of Acceptance

  • User Story Title

  • Remembering the title format (described above), substitute [user type] for whatever you enter here. Examples are "author", "sales manager", "administrator", etc.

    As a/an ...

  • Substitute the [feature] tag in the title for whatever you want to enter here. Keep in mind that the more specific the feature is in scope and descriptiveness - i.e. "spell checker" vs "editor" - the less time we're likely to spend on evaluating how to implement the feature.

    "I want "...

  • Substitute the [benefit] tag in the user story title for the value you enter here. A benefit should be something specific/tangible the user type will receive from the feature.

    "So I "...

  • Conditions of Acceptance

  • What are the list of conditions that need to be met by the [user type] to realize the [benefits] of the [feature]?

    Create as long of a list of single-sentence conditions (see the above example) as you need to

  • +-
  • This field is for validation purposes and should be left unchanged.

Leave a Reply

Your email address will not be published. Required fields are marked *