IIBA-AAC practice question 10 of 10

While quality checking the written user stories, the team ensures one of the components included in the attributes of a user story is:

Full set: 85 questions

Domain Delivery Horizon

Answer options
A: The explanation of the story’s cost
B: The stakeholder responsible for testing
C: The benefit or business value received by the user when the story is implemented Correct answer
D: The title describing the goal of the delivery cycle
Correct Answer:
C. The benefit or business value received by the user when the story is implemented
Explanation

A well-formed user story traditionally follows the "As a , I want , so that " template. The third component, the "so that" clause, is crucial as it explicitly defines the benefit or business value the user gains upon the story's implementation. This element provides the context and rationale ("the why") for the development team, which is essential for making correct implementation decisions and for prioritizing the story against others. Quality checking ensures this value proposition is clear, as delivering value is a core principle of agile development.

Why Incorrect

A. The explanation of the story’s cost: Cost is an estimation attribute used for planning and prioritization, not a fundamental component of the user story's narrative structure itself.
B. The stakeholder responsible for testing: This information is typically part of the team's workflow, acceptance criteria, or Definition of Done, not a core attribute of the user story's description.
D. The title describing the goal of the delivery cycle: The goal of a delivery cycle (e.g., a Sprint Goal) is a higher-level objective that a collection of user stories helps achieve, not an attribute of an individual story.

References

International Institute of Business Analysis (IIBA). (2017). Agile Extension to the BABOK® Guide (Version 2).

Section 7.16.2

Elements: This section details the three primary elements of a user story: Role

Goal

and Benefit (or Motivation). It explicitly states

"The benefit describes the business value the user role receives when the story is implemented." This directly supports the correct answer.

Section 7.16.3

Usage Considerations: This section discusses the INVEST criteria for quality user stories

where "V" stands for "Valuable." It states

"A user story must be valuable to the customer... The 'so that' clause of the user story format is intended to articulate the value." This reinforces that the benefit is a key quality attribute.

Scroll to Top