O'Reilly logo

User Stories Applied: For Agile Software Development by Mike Cohn

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

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?

Answer: See Table B.1.

Table B.1. Answer to Question 1.3.

image

1.4 What advantages do requirements conversations have over requirements documents?

Answer: Written documents imply a precision that they can’t back. User stories, ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required