BUSINESS-ANALYST practice question 16 of 35

Universal Containers has asked a business analyst (BA) to assist the sales management team with a request for a new picklist field called "Lost…

Full set: 310 questions
Universal Containers has asked a business analyst (BA) to assist the sales management team with a request for a new picklist field called "Lost Reason" on the Opportunity object with the goal of improving pipeline reports. After mapping the managers to the sales leader persona and obtaining feedback from them, the BA has discovered that the managers want to better understand Closed/Lost Opportunities so they can help sales teams close more deals. Which option should the BA use to construct the user story?
Answer options
A: As a sales leader, I want to see more details on Closed/Lost Opportunities so I can help the sales team improve close rates. Correct answer
B: As a sales team member, I need additional enablement training and reporting information to help the improve close rates.
C: AS a sales leader, I need a new "Closed/Lost Reason" picklist field on Opportunities and better reports to help the sales team improve close rates.
Correct Answer:
A. As a sales leader, I want to see more details on Closed/Lost Opportunities so I can help the sales team improve close rates.
Explanation

A user story should focus on the user's need and the value they will receive, not the specific technical solution. The standard format is: "As a [persona], I want [goal], so that [value/outcome]." Option A perfectly follows this structure. It identifies the sales leader as the persona, the goal of seeing more details, and the value of helping the team improve close rates. This format clearly communicates the business need without prematurely defining the implementation.

Why Incorrect

B. This option incorrectly identifies the persona as a "sales team member" when the request originated from sales management (leaders).
C. This option is too prescriptive. It dictates the solution ("new picklist field" and "better reports") within the user story, which violates the principle of focusing on the "what" and "why," not the "how."

References

1. Salesforce Trailhead, User Story Creation: Create User Stories. This unit explicitly defines the user story structure as "As a [who], I want [what], so that [why]." Option A is a textbook example of this format. (trailhead.salesforce.com/content/learn/modules/user-story-creation/create-user-stories)

2. Salesforce Architects, Well-Architected: Implementation Lifecycle. The documentation on Agile delivery emphasizes that user stories should describe functionality from a user's perspective, focusing on the value delivered rather than technical specifications. (architect.salesforce.com/well-architected/implementation-lifecycle/agile-delivery)

3. Cohn, M. (2004). User Stories Applied: For Agile Software Development. Addison-Wesley. Chapter 2, "Writing Stories," establishes the "Role-Feature-Reason" template, which directly corresponds to the "As a..., I want..., so that..." format.

Scroll to Top