User Stories and Users

Quiz Summary

0 of 15 Questions completed

Questions:

You have already completed the quiz before. Hence you can not start it again.

Quiz is loading…

You must sign in or sign up to start the quiz.

You must first complete the following:

Results

Quiz complete. Results are being recorded.

Results

0 of 15 Questions answered correctly

Your time:

You have reached 0 of 0 point(s), (0)

Current
Review
Answered
Correct
Incorrect

Question 1 of 15

1. Question
User stories are a variation on the use case.
- True
- False
Correct

Incorrect
Question 2 of 15

2. Question
A variation on Humphrey’s law suggests what about software requirements?
- Requirements don't really matter.
- Requirements can't be known until the system is built.
- Requirements should be locked in before we start development.
- The user should NEVER review a user story.
Correct

Incorrect
Question 3 of 15

3. Question
What are the three most important attributes of a user story that you will always want to capture and record?
- Size
- Who wants it
- Why they want it
- Why its valuable
- When they want it
- What they want to do
Correct

Incorrect
Question 4 of 15

4. Question
The three C’s about user stories refer to which of the following?
- Correlation (dependencies)
- Cost (to build)
- Card (should be short)
- Clarity (easily understood)
- Confirmation (acceptance criteria)
- Counter Proposal (alternatives to this story)
- Conversation (story is a basis for discussion)
- Causation (the root cause of the need)
Correct

Incorrect
Question 5 of 15

5. Question
Why is a user story a good descriptor of a user requirement but a poor source of documentation?
- User stories aren't properly documented.
- User stories can't be organized into proper chapters.
- User stories don't support diagrams.
- User stories are a moment-in-time view of a customer need.
Correct

Incorrect
Question 6 of 15

6. Question
User stories don’t have to be written on a card, but what’s the significance of using the symbolism of a card?
- It enables planning poker.
- It's just a hold over from the days before backlog management tools.
- It's encourages us to keep user stories short and self-contained.
- It allows us to hand the user story to a customer for their review.
Correct

Incorrect
Question 7 of 15

7. Question
Under what conditions might a user story NOT be an effective format for a requirement?
- When working on applications that do not have users.
- When addressing system requirements (language, frameworks, regulations).
- When building interfaces between systems.
- When the user will never be directly involved in development.
Correct

Incorrect
Question 8 of 15

8. Question
To what artifact does “confirmation” in Ron Jefferies 3 C’s refer?
- Assessment criteria
- Confirmation criteria
- Confirmation bias
- Assessment findings
Correct

Incorrect
Question 9 of 15

9. Question
The meaning of a Product Backlog Item is communicated to the Scrum Development Team by who and/or what?
- By the customer via email
- By the product owner via text messages
- By the Scrum Master via specification
- By the business analyst via Powerpoint
- By the product owner via conversation
Correct

Incorrect
Question 10 of 15

10. Question
Select one common approach for learning more about your customer.
- Studies in National Geographic magazine.
- Personas
- Surveillance
- Psychic evaluation
Correct

Incorrect
Question 11 of 15

11. Question
Can a Product Owner can be the subject of a persona?
- No
- Yes, for defects when the Product Owner wants something fixed.
- No, unless the Product Owner is ALSO a developer.
- Yes, if a Product Owner IS a role that uses the application.
Correct

Incorrect
Question 12 of 15

12. Question
What does a Journey Map help explain about your customer?
- Where they want to go on vacation.
- What they like and dislike about dealing with your product.
- Which of your competitor's they looked at first (in order to explain their beliefs).
- Where they go after using your product.
Correct

Incorrect
Question 13 of 15

13. Question
A user story should reflect ________________________.
- The desires of the product owner
- The solution the dev team plans to build
- The business strategy related to the functionality described.
- The problem the user wants solved.
Correct

Incorrect
Question 14 of 15

14. Question
In terms of a user story, what’s the difference between an output and an outcome?
- Output is measured in lines of code, outcomes in lines of comments.
- Nothing, they are the same thing.
- Output is measured in hours, outcomes in goals.
- Output is about functionality created, outcomes is about value produced.
Correct

Incorrect
Question 15 of 15

15. Question
You are repeatedly having difficulty deciding about which of two personas to use as the user in a user story. The story would be correct either way. What might that be telling you about your persona definitions?
- Nothing, you have to have two stories, one for each persona.
- You have two personas that might not really be different people.
- Nothing, write the user story to encompass both user personas.
- You're not building the right application.
Correct

Incorrect

Quiz Summary

Information

Results

Results

Categories

1. Question

2. Question

3. Question

4. Question

5. Question

6. Question

7. Question

8. Question

9. Question

10. Question

11. Question

12. Question

13. Question

14. Question

15. Question