CBAP · Question #40
You are the business analyst for your organization. You are currently working with Steve on the organize requirements process. You and Steve have elected to use the user stories approach for this…
The correct answer is C. Stakeholders' objectives are described to identify the requirements that the solution will need. The user stories approach organizes requirements by articulating stakeholder objectives and the outcomes the solution must achieve, not by recording interview narratives or treating raw experiences as requirements.
Question
You are the business analyst for your organization. You are currently working with Steve on the organize requirements process. You and Steve have elected to use the user stories approach for this process. What is the user stories approach for requirements organization?
Options
- AStakeholders' experiences equate to the stakeholder requirements.
- BStakeholders are interviewed and their experiences are recorded to help identify the requir
- CStakeholders' objectives are described to identify the requirements that the solution will need
- DStakeholders are interviewed and their stories are recorded as part of the requirements.
How the community answered
(44 responses)- A5% (2)
- B7% (3)
- C75% (33)
- D14% (6)
Why each option
The user stories approach organizes requirements by articulating stakeholder objectives and the outcomes the solution must achieve, not by recording interview narratives or treating raw experiences as requirements.
Equating stakeholder experiences directly to requirements skips the analysis step and conflates elicitation input with structured requirements, which is not the user stories method.
Recording interview experiences describes an elicitation documentation practice, not the user stories format used to organize and express requirements.
User stories express requirements from the perspective of stakeholder objectives - typically structured as what a stakeholder wants to accomplish and why - so that the solution can be designed to fulfill those goals. This approach keeps requirements outcome-focused and tied to business value rather than to how information was gathered or what was said during elicitation.
Recording stories from interviews describes capturing elicitation session notes, not structuring requirements as user stories tied to stakeholder objectives.
Concept tested: User stories approach for organizing requirements
Source: https://www.iiba.org/standards-and-resources/babok/
Topics
Community Discussion
No community discussion yet for this question.