REVENUE-CLOUD-CONSULTANT practice question 3 of 15

Which three are key steps when documenting user stories?

Full set: 90 questions
Answer options
A: Know which business process the requirement supports to categorize the user story Correct answer
B: Identity the actor or personas in this user story Correct answer
C: Design the solution while the business process is being defined
D: Document user acceptance test scripts for the user story.
E: Identify the acceptance criteria or result for satisfying the user story. Correct answer
Correct Answer:
A. Know which business process the requirement supports to categorize the user story; B. Identity the actor or personas in this user story; E. Identify the acceptance criteria or result for satisfying the user story.
Explanation

A well-formed user story follows the "As a [persona], I want [goal], so that [reason]" structure. Identifying the actor/persona (B) is the first part. Understanding the business process (A) provides the context or the "reason." Identifying the acceptance criteria (E) defines the "goal" and what constitutes a successful outcome. These three elements are fundamental to creating a clear, testable requirement that the development team can understand and implement. They ensure the story is independent, negotiable, valuable, estimable, small, and testable (INVEST).

Why Incorrect

C. Designing the solution is a subsequent step after the user story (the "what") is clearly defined and prioritized.
D. While acceptance criteria are key, writing full test scripts is part of the quality assurance phase, not the initial story documentation.

References

1. Salesforce Partner Community, Consultant's Guide to User Stories, "Anatomy of a User Story". This guide outlines the core components: Role (Who), Goal (What), and Benefit (Why), which directly correspond to options A, B, and E.

2. Salesforce Architects, Well-Architected - Composable, "Define Business Value". This documentation emphasizes defining business value and outcomes (Acceptance Criteria) and understanding the business process context for any requirement.

Scroll to Top