BA-201 · Question #139
A business analyst is gathering requirements for an automation that triggers tasks when an opportunity status changes. The requirement is that the system must alert the finance team when an opportunit
The correct answer is A. As a finance team member, I need to know when an opportunity is won that I can set up a billing. A well-written user story follows the format: 'As a [persona/role], I need [what] so that [why/benefit].' Option A correctly identifies a human actor (finance team member), a clear need (to know when an opportunity is won), and a business justification (set up a billing account).
Question
A business analyst is gathering requirements for an automation that triggers tasks when an opportunity status changes. The requirement is that the system must alert the finance team when an opportunity is won. What is an example of a well-written user story in this scenario?
Options
- AAs a finance team member, I need to know when an opportunity is won that I can set up a billing
- BAs an opportunity is won, task must be created for the finance team to set up a billing account
- CAs the system, it need to alert the finance team when an opportunity is won so they can set up a
How the community answered
(26 responses)- A85% (22)
- B12% (3)
- C4% (1)
Explanation
A well-written user story follows the format: 'As a [persona/role], I need [what] so that [why/benefit].' Option A correctly identifies a human actor (finance team member), a clear need (to know when an opportunity is won), and a business justification (set up a billing account). Option B is written from the perspective of the system event ('As an opportunity is won'), not a human user, which violates user story conventions. Option C uses 'As the system,' which is also not a valid user story persona - user stories must be written from the perspective of a person or role, not the system itself.
Topics
Community Discussion
No community discussion yet for this question.