Which technique is commonly used for requirement elicitation?

Interviews are a widely recognized technique for requirement elicitation due to the direct interaction they facilitate between the business analyst and stakeholders. This method allows for in-depth conversations that can uncover detailed insights about the stakeholders' needs, expectations, and possibly hidden requirements that might not surface through more indirect means.

Through interviews, the analyst can ask open-ended questions, gather information on specific topics, and explore responses that prompt further discussion. This technique also provides an opportunity to clarify misunderstandings and ask follow-up questions, which fosters a richer understanding of the requirements being gathered. The ability to adapt the conversation flow based on stakeholder responses makes interviews a flexible and effective approach for ensuring comprehensive requirement gathering.

While other techniques such as cost-benefit analysis, risk assessment, and quality assurance testing have their own important roles in the overall requirements lifecycle, they are not primarily focused on eliciting requirements. For instance, cost-benefit analysis assesses the financial implications of a project rather than gathering requirements, risk assessment identifies potential issues, and quality assurance testing ensures that the outputs meet specified requirements rather than discovering what those requirements are. Thus, interviews stand out as a pivotal method specifically geared toward eliciting requirements effectively.