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, ...
Get User Stories Applied: For Agile Software Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
