User Stories

5 minutes 5 Questions

User Stories are an integral part of Scrum and express requirements from an end user’s perspective. They are a simple technique for describing the desired functionality from the viewpoint of the user. User Stories focus on the value that the requirement brings to the user, rather than on system imp…

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

PSM I - User Stories Example Questions

Test your knowledge of User Stories

Question 1

A developer realized that a User Story requires knowledge in a specific technical area that was overlooked earlier. Who should the developer approach with this information?

The customer to ask for more details. Nobody, as it is the developer's responsibility to learn the needed new skills. The other team members during the Retrospective. The Scrum Master, so that they can address it in the Daily Scrum.

Correct Answer: The Scrum Master, so that they can address it in the Daily Scrum.

In a typical Scrum framework, when a developer realizes that a User Story requires specific technical knowledge that was overlooked earlier, they should approach the Scrum Master with this information. This is because the Scrum Master is primarily responsible for facilitating daily scrum, sprint planning, sprint demo and retrospective meetings. The Scrum Master helps the team to identify and fill the Agile skill gaps and resolve issues related to resources or tools. The other answers are incorrect because: (1) Contacting the customer to ask for more details does not necessarily help in acquiring the required technical knowledge and could confuse the customer with technical details. (2) While learning new skills is important, it is not solely the developer's responsibility to learn new skills whenever an unknown field comes up. That is a team responsibility and it may take significant time that may delay the project. (3) Discussing this in the Retrospective would be too late in the Scrum process, as this meeting occurs after the Sprint ends. The issue needs to be addressed as soon as it is discovered for the sake of the project timeline.

Question 2

When writing user stories, which method is preferred when specifying user roles?

Using arbitrary labels like 'person A' and 'person B' Using department names from within the organization Using the developer's name Using only the terms 'customer' or 'user' Using only job titles Using personas and specific user types

Correct Answer: Using personas and specific user types

Using personas and specific user types helps the team relate to the user story and empathize with the user's needs, this aids in creating a more effective and valuable solution.

Question 3

A developer completed the user story and moved it to the 'Done' column, but the Product Owner discovered that not all acceptance criteria were met. What should the team do?

Reassign the user story to a different developer Keep the user story in the 'Done' column Put it on hold until the next sprint Ignore the feedback and focus on the next story Mark it as rejected and start a new user story Move the user story back to 'In Progress' and complete the missing tasks

Correct Answer: Move the user story back to 'In Progress' and complete the missing tasks

When the acceptance criteria are not met, the user story should be moved back to 'In Progress' so that the required tasks are completed, ensuring the product meets the desired user outcomes.

🎓 Unlock Premium Access

Professional Scrum Master I + ALL Certifications