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?
A. Include the V2MOM structure
B. Include who, What, and why
C. Include technical details
B. Include who, What, and why
Explanation:
The lead BA should tell the junior BAs to include who, what, and why in a user story. Who,
what, and why are the essential elements of a user story that define who is requesting a
feature or functionality (the user or persona), what they want to achieve or accomplish (the
goal or value), and why they want it (the reason or benefit). A user story should include
who, what, and why because it helps to:
Clarify the scope, functionality, and quality of the user story.
Provide a basis for testing and validating the work done.
Ensure that it meets the user’s needs and expectations The other options are
either incorrect or irrelevant. Option A is incorrect because V2MOM is a structure
that defines an organization’s vision, values, methods, obstacles, and measures,
not a user story. Option C is incorrect because technical details are not part of a
user story, but rather part of acceptance criteria or design specifications.