Last modified 13 years ago Last modified on 06/02/06 14:37:40

About user stories

User stories are written as tickets with type story.

See user story drafts and ideas

See all user stories

A good story is:

  • Independent: minimal dependencies between stories
  • Negotiable: they are not contracts, but can be commented and refined
  • Valuable to users
  • Estimatable: developers can estimate the amount of work the story requires
  • Small: can be implemented in 1-2 weeks (larger stories are Epics)
  • Testable: can be verified with an automated test (not a unit test, though)

User stories should not be too detailed. The customer (or product owner) can provide the details when implementation in starting (=when the enhancement ticket is being written).

Miscellaneous notes

Read about user stories from Wells, D. (1999). Extreme Programming: A gentle introduction.

An example user story from Fle3 project: