User Stories in Scrum test - Professional Scrum Master I questions

Question 1

As a Scrum Master, your team is struggling to understand the Role-Feature-Reason template. How would you explain the 'Role' part of this template in relation to a task for creating a 'Delete Account' feature?

The 'Role' specifies who benefits from the feature, such as 'As an Account Owner'. 'Role' is the overall goal or outcome the feature aims to achieve, like enhancing user security. 'Role' outlines the specific tasks and actions that the user or system must perform to implement the feature, including steps like accessing account settings, selecting the 'Delete Account' option, and confirming account deletion. This comprehensive outline ensures clarity in feature execution. The 'Role' describes the technical specifications needed for the feature, detailing system requirements.

Correct Answer: The 'Role' specifies who benefits from the feature, such as 'As an Account Owner'.

In the context of the Role-Feature-Reason template, the 'Role' part specifically focuses on identifying the primary user or beneficiary of the feature in question. It is not about the technical specifications, the high-level goal, or the detailed steps required to implement the feature. Therefore, the correct answer is that the 'Role' specifies who benefits from the feature, such as 'As an Account Owner', which helps to clearly define the target audience for whom the feature is being created.

Question 2

As a Product Owner, you are tasked to deliver a feature allowing users to send direct messages within the app. Which of the following is the correct way to represent this using the Role-Feature-Reason template?

As a registered user, I want to send direct messages, so that I can communicate privately with other users. As a registered user, I want the app to store message history, so I can reference past conversations. Given a user's preference for privacy, the system shall provide an encrypted direct messaging service to ensure secure communication between authenticated participants, leveraging state-of-the-art cryptographic standards. Enable private messaging feature for enhanced user interaction within the platform.

Correct Answer: As a registered user, I want to send direct messages, so that I can communicate privately with other users.

The correct answer follows the Role-Feature-Reason (User Story) template, clearly stating the role ('As a registered user'), the feature ('I want to send direct messages'), and the reason ('so that I can communicate privately with other users'). The wrong answers, while related, either focus on a different aspect of app functionality, describe the feature in a generic way without following the User Story format, or provide an overly technical and detailed implementation strategy, which makes them incorrect choices in the context of expressing user needs through User Stories.

Question 3

As a Scrum Master, you're overseeing a project to create an online payment system, which is a novel concept for the team. Which statement best illustrates the Role-Feature-Reason template to clarify the user story?

We need a system where shoppers can choose between using credit cards or digital wallets to make their payments more flexible and convenient. As a security analyst (Role), I want to implement advanced encryption techniques (Feature) to ensure that the shoppers' payment information is securely transmitted (Reason). As an online shopper (Role), I want to integrate my digital wallet (Feature), so that I can make faster payments without re-entering my card details (Reason). A shopper expects the payment system to automatically fill in their payment details by scanning their cards.

Correct Answer: As an online shopper (Role), I want to integrate my digital wallet (Feature), so that I can make faster payments without re-entering my card details (Reason).

The correct answer clearly follows the Role-Feature-Reason template, which is used to structure user stories in Scrum. This template ensures that the user story is focused on the user's needs, what they want to achieve, and why. Wrong Answer 1 does not follow the template and describes a feature without specifying the user's role or the underlying reason. Wrong Answer 2, although structured correctly, shifts the focus from the end-user to an internal role, which dilutes the intent of addressing the end-user's story. Wrong Answer 3 is a longer response but lacks the structure and clarity provided by the Role-Feature-Reason template, making it a less effective user story.

User Stories in Scrum

PSM I - User Stories in Scrum Example Questions

Question 1

Question 2

Question 3

Go Premium