Skip to main content
Enterprise Agile Planning icon with arrows

This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.

Last Updated Jun 21, 2007 — Enterprise Agile Planning expert

User story examples and counterexamples

Enterprise Agile Planning

People who share my background in traditional requirements analysis often have a hard time coming up with product backlog items representing thin vertical slices of potentially-shippable product. Here are some good and bad examples that people have found useful.


User stories may assume template form (see User Stories Applied by Mike Cohn):

  • “As a [role] I can [function] so that [rationale].”

or expressed as noun phrase:

  • “Image clipboard”

or a one to two sentence story (ideally a testable assertion):

  • “Busy streets are highlighted on the map.”

User stories, like all product backlog items, should contain or clearly imply acceptance criteria (definition of “done”). Write these on the back of the index card, or in the “description” field if you’re using an electronic tool.

Bill Wake has given us the INVEST mnemonic to help remember the characteristics of a well-formed user story:

  • I – Independent
  • N – Negotiable
  • V – Valuable
  • E – Estimable
  • S – Small
  • T – Testable


What does this look like in practice?

  1. A bank customer can change his PIN.
    • Acceptance criteria: ….
  2. As a student, I can find my grades online so that I don’t have to wait until the next day to know whether I passed.
    • Acceptance criteria: ….
  3. One level of undo
    • Acceptance criteria: ….
  4. As a book shopper, I can read reviews of a selected book to help me decide whether to buy it.
    • Acceptance criteria: ….
  5. As an author, I want the spell checker to ignore words with numbers so that only truly misspelled words are indicated.
    • Acceptance criteria: ….


How do we know when we’re missing the mark? Ultimately “User stories are a promise for a conversation” (Ron Jeffries). If product owner and team both know what they mean, you’re off to a good start. But you can probably save some time by avoiding the common pitfalls below:

  1. “Design brochure layout.”
    • Drawbacks: not Independent, no business Value. This is a task representing a horizontal architectural layer or phase. The architecture will be done in a vacuum, possibly contributing to analysis paralysis.
    • Better: “As a dog owner, I can find a meal schedule on the brochure so I know whether this doggy day care center is appropriate for my hungry dog.”
      • This will lead to only the necessary amount of design to support this sprint’s features. The layout might change the next sprint, but rework is cheaper than no work.
  2. “Write game rules.”
    • Drawbacks: not Independent, no business Value, not Small.
    • Better: “As a newbie game player, I want to know who goes first so we can start the game.”
    • Better: “As a competitive gamer, I want a way to leapfrog my opposing players.”
  3. “I want the brochure to be colorful.”
    • Drawbacks: not Independent, not Estimable (without knowing other features of brochure), not Small.
      • This is an easy trap for those of us who grew up with the habit of writing “the JFIDM _shall_ comply with the IEEE-488 interface specification.”
    • Better: Use “colorful” and other cross-cutting requirements as acceptance criteria on each of the specific features in the backlog they apply to.
  4. “As product owner, I want a list of highly-rated restaurants on the brochure.”
    • Drawbacks: It’s not only about you!
    • Better: Focus on your end users and stakeholders. “As a gourmet tourist, I want a list of highly-rated restaurants on the brochure.”
    • Better: “As the Chicago Public Health Department, I want warnings about restaurants that serve raw ingredients so that tourists don’t get sick on our dime.”
  5. “Play test the game.”
    • Drawbacks: Not Independent. Encourages phase-wide development.
    • Better: Make testing, refactoring, etc. a default acceptance criteria on every product backlog Item.
      • But: If you failed to fully test and refactor in previous sprints, you are in technical debt! You are already working on a legacy product. In this case you may need to make testing and refactoring first-class product backlog items to make up for your sins. This practice is controversial, and technical debt repayment cannot honestly be called a user story. A PBI that’s not a user story may still be useful as a starting point for a conversation about how to reduce technical debt incrementally while continuing to deliver new value.

 User stories are simple thing. “Simple” is often not the same as “easy.” Happy unlearning!

Michael James
Software process mentor
Watch example user stories being extracted from epics (and estimated in story points) in a backlog grooming meeting:

Backlog Grooming Meeting aka Backlog Refinement Meeting
For a general scrum reference, see the six-page Scrum Reference Card.
To learn more about the scrum master’s role, see the Scrum Master’s Checklist and the Introduction to Scrum video.

More from the Blog

View more
Jul 05, 2022

How to bring external data to Agility

Enterprise Agile Planning
Data integrations occur every day Data and system integrations tend ...
Read More Government Cloud
Apr 12, 2022 Government Cloud receives FedRAMP Authorization through sponsorship from the United States Department of Veterans Affairs

Enterprise Agile Planning
Flagship Agility solutions can effectively scale agile deve ...
Read More
Nov 22, 2021

What are the qualities of highly effective agile teams?

Enterprise Agile Planning
A team is the core unit of productivity in an agile organization. Wher ...
Read More
Nov 15, 2021

How an open-first attitude revolutionized government tech development

Enterprise Agile Planning
Public perception of government is often that it is slow-moving, reluc ...
Read More
Contact Us