User Story
The unit of requirements gathering is the User Story, which is user-visible functionality that can be developed within one iteration or less.
Introduction
User Stories focus on user needs.
User Stories are roughly three sentences long written by customers in plain English to describe things they need the system to do for them. User stories provide only enough detail to make a reasonably low risk estimate of how long the story will take to implement. When the time comes to implement a story, the developers and customers will hash out the details face-to-face.
The stories are used to create time estimates for release planning. Customers write the stories, developers estimate how long the stories might take to implement. Each story will get an estimate in Ideal Pair Days. This estimate is how long it would take a developer pair to implement the story in code if there were no distractions, no other assignments, and we knew exactly what to do. Longer than 10 days means we need to break the story down further. Less than 1 day and we are at too detailed a level, combine some stories.
Stories
Anyone can create a user story describing what they need. Don't worry about getting it right the first time ... just click edit/save :-)
Ohh, and don't forget to add Category:User Story to the page.
