March 2004
Intermediate to advanced
304 pages
6h 12m
English
Content preview from User Stories Applied: For Agile Software DevelopmentBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
Start your free trial
Appendix B. Answers to Questions
Chapter 1, An Overview
1.1 What are the three parts of a user story?
Answer: Card, Conversation, and Confirmation.
1.2 Who is on the customer team?
Answer: The customer team includes those who ensure that the software will meet the needs of its intended users. This may include testers, a product manager, real users, and interaction designers.
1.3 Which of the following are not good stories? Why?
Table B.1. Answer to Question 1.3.
1.4 What advantages do requirements conversations have over requirements documents?
Answer: Written documents imply a precision that they can’t back. User stories, ...