User Stories

 

User stories are written by the customer with designers.

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

from http://www.agile-software-development.com

and http://www.extremeprogramming.org/rules/userstories.html

User Stories are a simple way of capturing user requirements throughout a project - an alternative to writing lengthy requirements specifications all up-front. They are written in the everyday language of the user. They are used for the specification of requirements and lead to a release plan.

1. Card
2. Conversation (focus on user needs)
3. Confirmation (test cases, must be written in advance of implementation)

 

Benefits

• small chunks - more easily implemented
• close customer contact
• good for projects with poorly understood requirements

Challenges

• require close customer contact
• requires competent developers
• good conversation starters, but bad documentation trackers