The business analyst (BA) at Cloud Kicks is having a hard time documenting a user story to change an existing Opportunity flow for sales users. The architect expressed their concerns to the BA that…

Question

Options

• AWrite the user story without making any assumptions about how it will be implemented or which
• BAsk the development team to investigate and document all affected components before the story
• CSchedule additional discovery sessions with the sales users to understand what will be impacted

• A
  9% (4)
• B
  19% (9)
• C
  72% (34)

Explanation

When the scope of impact for a change is unclear, the BA's role is to facilitate discovery rather than either writing incomplete stories or delegating investigation to developers. Option A (writing the story without assumptions) would produce a vague story that still doesn't resolve the architect's concern. Option B (asking developers to investigate) skips the BA's responsibility to gather requirements and understand user context. Option C is correct because additional discovery sessions with the sales users - who actually use the flow - will surface which scenarios, related processes, and components are affected, giving the team the comprehensive understanding needed before implementation begins.

No community discussion yet for this question.