Using User Stories

Since learning about them some nine years ago, I’ve found User Stories to be much handier for expressing what the system should do than the monolithic requirements documents I dealt with in the past.  User Stories have a number of advantages:

  • They can easily be shuffled into a different order.
  • You generally know (by the acceptance criteria) whether or not they’re done.
  • They don’t contain a lot of duplicated or contradictory detail.
  • The detail gets elaborated when it’s needed (rather than a long time prior, letting the details get out-of-date and/or forgotten).

I’ve created a two-page handout on writing and splitting User Stories.  I’m publishing it here in case it helps others.  And I would welcome any feedback on it.

7 Replies to “Using User Stories”

  1. I’ve also found Gerard Meszaros Storyotypes idea to be pretty useful [] and I think Dan Rawsthorne did some extending of the idea []. Also Alistair Cockburn’s brief summary relating use cases and user stories helpful (not entirely clear to me yet, but helpful) []. Maybe some of these resources would be useful to users of the handout.

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.