1
Q
What is a user story?
A
A user story describes functionality that will be valuable to either a user or purchaser of a system or software. User stories are composed of three aspects:
- a written description of the story used for planning and as a reminder
- conversation sabout the story that serve to flesh out the details of the story
- tests that convey and document details and that can be used to determine when a story is complete
2
Q
What is a user story template?
A
- As a [role] I can [function] so that [rationale]
- Or
- Noun phrase: “Image clipboard”
3
Q
What are the characteristics of a good story?
A
- I –Independent
- N –Negotiable
- V –Valuable to users or customers
- E –Estimable
- S –Small
- T-Testable
4
Q
Why user stories?
A
- User stories emphasize verbal rather than written communication.
- User stories are comprehensible by both you and the developers.
- User stories are the right size for planning.
- User stories work for iterative development.
- User stories encourage deferring detail until you have the best understanding you are going to have about what you really need.
5
Q
What are the techniques for gathering user stories?
A
–User interviews
–Questionnaires
–Observation
–Story-Writing workshops
