Inputs to prepare for elicitation include:

Question

Options

• Ainformation management approach and solution scope.
• Bneeds and stakeholder engagement approach.
• Cfuture state description and risk analysis results.
• Drequirements and designs.

• A
  2% (1)
• B
  89% (39)
• C
  2% (1)
• D
  7% (3)

Explanation

Option B is correct because preparing for elicitation requires knowing what you're trying to uncover (needs) and who to engage and how (stakeholder engagement approach) - these two inputs directly inform the planning of elicitation activities, including selecting techniques and scheduling sessions.

Option A is wrong because the information management approach governs how requirements are stored and traced (a later concern), and solution scope is typically an output of analysis, not an input to elicitation preparation.

Option C is wrong because a future state description and risk analysis results emerge from analysis and planning activities that occur later in the process - you wouldn't have these fully defined when preparing to elicit in the first place.

Option D is wrong because requirements and designs are outputs of the broader elicitation and analysis process, not inputs. Elicitation exists precisely to discover requirements, so they can't precede it.

Memory tip: Think "Who + What" - you need to know what problem/need you're addressing and who (stakeholders) you'll engage before you can plan any elicitation session. Needs + Stakeholder Engagement = the foundation of preparation.

No community discussion yet for this question.