Here are some helpful pointers for writing User Stories
A Story template
- "As a <User or role>
- I want <Business Functionality>
- So that <Business Justification>”
Example:
- As a Account Holder,
- I want to be able to withdraw funds from my checking account,
- So that I can buy some bling.
Stories are not
- "mini" Use Cases
- a complete specification
- a contract
- intended to be interpreted without a Product Owner
User Stories guidelines
- Testable - Tangible acceptance tests can be written against any delivered software
- The scope of the User Story is manage-able enough for the team to provide an Estimate
- Independent and do not rely on other Stories
- Sized appropriately.. Have a level of effort which the team can comfortably achieve in the duration of a single iteration
More information can be found http://www.mountaingoatsoftware.com/agile/user-stories