Which of the following best represents the standard format of a user story?

Question

BlackTom AI · Accepted Answer

To determine which option aligns with the standard format of a user story, we first restate the question and list the answer choices clearly.
Option 1: "When [event] occurs, then [response] should happen." This resembles a simple conditional requirement or use-case statement, but it does not follow the classic user story structure that centers on the user and their goal.
Option 2: "As a [user], I want [goal], so that [reason]." This phrasing explicitly begins with the user role, then states a goal, and finally explains the value or rationale, which is the hallmark of the standard user story format used in agile practices.
Option 3: "The system should perform [action] when the user clicks a button." This is more like a functional specification or a high-level acceptance criterion, and it focuses on system behavior rather than the user’s perspective and value.
Option 4: "If [condition] then [action] and [outcome]." This presents a conditional flow or rule but does not express the user’s role, goal, and the intended benefit, which are essential parts of a user story.

Now, evaluating each choice in terms of the core elements of a user story—who the user is, what they want to achieve, and why it matters—we can see distinct differences. The first option centers on events and responses, lacking the user role and value statement. The third option centers on system actions tied to a trigger but omits the user-centric perspective and justification. The fourth option emphasizes a condition-action-outcome pattern without anchoring the narrative to a specific user and their goal, thereby missing the motivational component.

In contrast, the second option directly follows the conventional user-story template: it starts with the user role, specifies a goal the user wants to achieve, and ends with the rationale or benefit. This structure supports clear communication, testability, and alignment with agile practices like INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable).

In summary, the reasoning behind preferring the second option rests on its explicit user-centered framing, its inclusion of both the goal and the value rationale, and its alignment with widely adopted agile storytelling conventions. The other options, while describing behaviors or rules, fail to capture the full user-story format that centers the user’s perspective and the intended value.

Note: When comparing formats, remembering that a user story typically answers: Who is the user? What do they want to achieve? Why is it valuable? helps distinguish the standard template from alternative specification styles.

CPT_S-322-PULLM-1-LEC Class Quiz-1

Which of the following best represents the standard format of a user story?

View Explanation

Log in for full answers

Similar Questions

The template of a user story is:

Which one of the following user stories is a complete user story with all the required detail?

A good quality user story does NOT have the following characteristic:

When a story is too big, it is sometimes referred to as:

Who is the source of Agile user stories?

User story is:

What is a key benefit of using user stories in Agile development?

A good quality user story does NOT have the following characteristic:

More Practical Tools for Students Powered by AI Study Helper

Homework AI Solver

Stylized AI Paper Writer

Plagiarism Checker Assistant

Citation AI Academic Writing Tool

In-Class Translation Assistant

AI Note Generator

AI Quiz Answers

Past Exam Questions from University Test Bank

Smart Practice Assistant

Adaptive Practice

Making Your Study Simpler