CAPM Practice: Determine how to gather requirements

Elicitation planning prevents ad hoc, incomplete requirements gathering. Planning identifies the right stakeholders, selects appropriate techniques for each situation, sequences activities logically, and prepares questions — making elicitation more efficient and complete.

**Why not A:** Creating the requirements documentation template is one small aspect of preparation, not the full scope of elicitation planning. Elicitation planning encompasses selecting techniques, identifying stakeholders, sequencing activities, preparing questions, and determining logistics for each elicitation session.

**Why not B:** Getting management approval before conducting interviews may be needed in some organizations, but it is not the definition of elicitation planning. Planning focuses on the strategic approach to elicitation itself, including which techniques to use, who to engage, and what to ask, not on authorization procedures.

**Why not D:** Writing out all requirements before meeting with stakeholders defeats the purpose of elicitation. Elicitation is the process of discovering requirements through stakeholder interaction. Pre-writing requirements before gathering input would bypass the discovery process and produce assumptions rather than validated requirements.