BA-201 · Question #247
A sales manager at Cloud Kicks recently learned about Salesforce Macros and believes service agents could benefit from the feature. The sales manager created the following user story: "As a service ag
The correct answer is C. Add a quantifiable reason why the feature is needed.. A well-formed user story follows the structure: 'As a [persona], I want [feature or goal] so that [quantifiable benefit].' The story as written - 'As a service agent I want Salesforce Macros to complete repetitive tasks faster' - is missing a measurable 'so that' clause. Simply s
Question
A sales manager at Cloud Kicks recently learned about Salesforce Macros and believes service agents could benefit from the feature. The sales manager created the following user story:
"As a service agent I want Salesforce Macros to complete repetitive tasks faster." What should the business analyst change to improve the user story?
Options
- AReplace the specific feature with a goal.
- BChange the user story to the sales manager persona.
- CAdd a quantifiable reason why the feature is needed.
How the community answered
(43 responses)- A19% (8)
- B9% (4)
- C72% (31)
Explanation
A well-formed user story follows the structure: 'As a [persona], I want [feature or goal] so that [quantifiable benefit].' The story as written - 'As a service agent I want Salesforce Macros to complete repetitive tasks faster' - is missing a measurable 'so that' clause. Simply saying 'faster' is vague and untestable. A better version would include a specific, quantifiable outcome, such as 'so that I can reduce average handle time by 20%.' While Option A (replacing the specific feature with a goal) is also a valid improvement, the more impactful fix identified by the answer is adding a measurable reason, which makes the story testable and outcome-oriented.
Topics
Community Discussion
No community discussion yet for this question.