User Stories

Question 1

What is a user story?

Answer 1

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:

1. a written description of the story used for planning and as a reminder
2. conversation sabout the story that serve to flesh out the details of the story
3. tests that convey and document details and that can be used to determine when a story is complete

Question 2

What is a user story template?

Answer 2

• As a [role] I can [function] so that [rationale]
• Or
• Noun phrase: “Image clipboard”

Question 3

What are the characteristics of a good story?

Answer 3

• I –Independent
• N –Negotiable
• V –Valuable to users or customers
• E –Estimable
• S –Small
• T-Testable

Question 4

Why user stories?

Answer 4

• 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.

Question 5

What are the techniques for gathering user stories?

Answer 5

–User interviews
–Questionnaires
–Observation
–Story-Writing workshops