BA-201 · Question #307
The sales team recently received training on a new sales methodology. When viewing an Opportunity in Sales Cloud, the sales manager wants the sales cycle to include new stages in addition to…
The correct answer is B. Who, what, and why. This answer states that using who, what, and why is what each user story should include for optimizing a very manual process in its Salesforce org. Who refers to the persona, which is a fictional representation of a typical user or stakeholder who will use or benefit from a…
Question
The sales team recently received training on a new sales methodology. When viewing an Opportunity in Sales Cloud, the sales manager wants the sales cycle to include new stages in addition to multiple custom fields. The business analyst is starting to construct user stories to support the new process. What should each user story include?
Options
- AValue, purpose, and need
- BWho, what, and why
- CWho, where, and how
How the community answered
(50 responses)- A8% (4)
- B88% (44)
- C4% (2)
Explanation
This answer states that using who, what, and why is what each user story should include for optimizing a very manual process in its Salesforce org. Who refers to the persona, which is a fictional representation of a typical user or stakeholder who will use or benefit from a feature or a functionality. What refers to the goal, which is what the user or stakeholder wants to accomplish with the feature or functionality. Why refers to the value, which is why the user or stakeholder wants to accomplish the goal, and how they will measure success. Using who, what, and why can help the BA to write effective user stories that capture and prioritize the requirements, and align them with the stakeholder value and expectations. https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick- look/use-user-stories-to-capture-requirements
Topics
Community Discussion
No community discussion yet for this question.