After the completion of the most recent sprint at Cloud Kicks (CK), the business analyst (BA) provided a demo of three user stories for the customer support solution to a senior executive. During the

Question

Options

• AConfirm each user story includes a clear who, what, and why.
• BUpdate the environment to use language specific to CK.
• CExplain that the term is a Salesforce industry standard.

• A
  75% (15)
• B
  15% (3)
• C
  10% (2)

Explanation

A well-formed user story follows the format: 'As a [who], I want to [what], so that [why].' If the user stories had clearly articulated the 'what' in business terms - describing the purpose and context of creating or closing a support ticket in CK's language - the executive would have understood the business value without relying on Salesforce jargon like 'case.' Confirming user stories include a clear who, what, and why ensures demos communicate business outcomes, not just system actions. Option B ('update the environment to use CK-specific language') addresses terminology in the UI, but the root issue is that the user story itself lacked sufficient business context to make the demo self-explanatory. Option C (explaining that 'case' is a Salesforce standard) is dismissive and does not improve future demos.

No community discussion yet for this question.