nerdexam
Salesforce

BA-201 · Question #41

The business analyst at Cloud Kicks is beginning to write user stories for its Salesforce implementation. Which three components should-be included when writing a user story?

The correct answer is A. Who, what, why. User stories follow the standard format: 'As a [Who], I want [What], so that [Why].' The 'Who' defines the persona or user role, the 'What' describes the desired functionality or feature, and the 'Why' explains the business value or benefit the user gains. This structure…

Elicit & Analyze

Question

The business analyst at Cloud Kicks is beginning to write user stories for its Salesforce implementation. Which three components should-be included when writing a user story?

Options

  • AWho, what, why
  • BWhen, where, why
  • CWho, when, why

How the community answered

(41 responses)
  • A
    90% (37)
  • B
    7% (3)
  • C
    2% (1)

Explanation

User stories follow the standard format: 'As a [Who], I want [What], so that [Why].' The 'Who' defines the persona or user role, the 'What' describes the desired functionality or feature, and the 'Why' explains the business value or benefit the user gains. This structure ensures stories are user-centered and value-driven. 'When' and 'Where' are not core components of a user story-they may appear in acceptance criteria or context but are not part of the standard three-part user story template. Omitting 'Who' or 'Why' results in stories that lack context and business justification, making them difficult to prioritize and develop against.

Topics

#User Stories#Requirements Elicitation#Agile Methodology#Business Analysis

Community Discussion

No community discussion yet for this question.

Full BA-201 Practice