Why would a business analyst (BA) want to define stakeholder assumptions?

Question

Options

• ATo determine needed organizational changes
• BTo assess model completeness
• CTo clarify requirements
• DTo manage risk

• A
  2% (1)
• B
  2% (1)
• C
  7% (4)
• D
  89% (51)

Explanation

Defining stakeholder assumptions is fundamentally a risk management activity - assumptions are unverified beliefs that, if wrong, can derail a project. By explicitly documenting them, the BA surfaces hidden risks so they can be monitored, validated, or mitigated before they cause problems.

• A (organizational changes) is wrong - identifying needed changes comes from analyzing requirements and gaps, not from cataloging assumptions.
• B (model completeness) is wrong - assumptions don't validate whether a model covers all scenarios; that's a separate analysis activity.
• C (clarify requirements) is a tempting distractor since assumptions often arise during requirements gathering, but clarification is a byproduct, not the primary purpose of defining assumptions.

Memory tip: Think "assumption = risk in disguise." If an assumption turns out to be false, something goes wrong - that's the definition of risk. BA → Define assumptions → Manage risk.

No community discussion yet for this question.