The lead business analyst (BA) at Cloud Kicks is putting together user Stories for the new sales process that will be implemented in Sales Cloud. The lead BA is advising junior BAS on how to construct

The correct answer is B. Include who, What, and why. A well-formed user story follows the standard template: 'As a [who], I want [what], so that [why].' This captures the persona (who benefits), the goal (what they need), and the business value (why it matters). Option B correctly identifies these three components. Option A (V2MOM)

Elicit & Analyze

Question

The lead business analyst (BA) at Cloud Kicks is putting together user Stories for the new sales process that will be implemented in Sales Cloud. The lead BA is advising junior BAS on how to construct a user story. What should the lead BA tell the junior BAs to include in a user story?

Options

AInclude the V2MOM structure
BInclude who, What, and why
CInclude technical details

How the community answered

(49 responses)

A
6% (3)
B
90% (44)
C
4% (2)

Explanation

A well-formed user story follows the standard template: 'As a [who], I want [what], so that [why].' This captures the persona (who benefits), the goal (what they need), and the business value (why it matters). Option B correctly identifies these three components. Option A (V2MOM) is a Salesforce strategic planning framework - Vision, Values, Methods, Obstacles, Measures - used for organizational goal-setting, not for writing individual user stories. Option C (technical details) should be excluded from user stories; technical implementation belongs in acceptance criteria or technical specifications, not in the story itself. The story should stay focused on business value, not how something is built.

Topics

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

Community Discussion

No community discussion yet for this question.

Full BA-201 Practice