During a workshop to understand Universal Containers’ current sales process, there seems to be some
disagreement between the North America and EMEA sales teams about the steps required to close a sale.
What should the business analyst do to gain consensus on the current opportunity process?
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?
During a workshop to understand Universal Containers’ current sales process, there seems to be some
disagreement between the North America and EMEA sales teams about the steps required to close a sale.
What should the business analyst do to gain consensus on the current opportunity process?
The business analyst at Universal Containers has been asked to train the client on how to write effective user
stories with acceptance criteria. The client provided this sample story.
User Story:
As a customer service agent, I need the ability to close support tickets.
Acceptance Criteria:
1. When viewing an open support ticket, a "Close Ticket" action is available.
2. When closing a support ticket, the agent is required to enter a "Close Reason".
3. After completing the close action, the status of the support ticket is set to "Closed".
What can be done to improve this user story?