SMC practice question 24 of 25

Which of the following is the correct format for writing a User Story?

Full set: 148 questions

Domain Plan and Estimate Phase

Answer options
A: As a {role/persona}, I should be able to {requirement} so that {benefit}. Correct answer
B: As a {role/persona}, I should be able to {benefit} so that {requirement}.
C: I should be able to {benefit}, as a {role/persona} so that {requirement}.
D: I should be able to {requirement} so that {benefit} as a {role/persona}.
Correct Answer:
A. As a {role/persona}, I should be able to {requirement} so that {benefit}.
Explanation

The standard and most widely accepted format for writing a User Story follows the "role-goal-benefit" template. This structure, often attributed to Connextra, ensures that the story captures three critical elements: who wants the functionality (the persona or role), what they want to achieve (the requirement or goal), and why they want it (the benefit or value). This format helps the team understand the user's perspective and the business value of the feature being developed.

Why Incorrect

B. This option incorrectly swaps the benefit and the requirement, leading to a confusing and illogical statement about the user's goal.
C. This option rearranges the components in a non-standard way that reduces clarity and deviates from the established best practice for User Story creation.
D. This option also uses a non-standard structure that is less intuitive and effective than the conventional "As a..., I want..., so that..." format.

References

1. ScrumStudy. (2017). A Guide to the Scrum Body of Knowledge (SBOK® Guide) (3rd ed.). Section 6.2, Page 128. "A User Story is usually written in the following format: As a , I want so that ."

2. Cohn, M. (2004). User Stories Applied: For Agile Software Development. Addison-Wesley Professional. Chapter 2. (While not a ScrumStudy source, it is a foundational text referenced in academic and university courseware on Agile and Scrum, establishing the standard format).

Scroll to Top