Which approach is appropriate for a simple requirements elicitation session with stakeholders?

• A. Force stakeholders to accept pre-made requirements.
• B. Set goals, ask open-ended questions, capture needs and constraints, document, validate with stakeholders.
• C. Ask only yes/no questions.
• D. Skip documentation.

Answer: (B)

A strong requirements elicitation session works best when you guide the conversation with clear goals, ask open-ended questions, capture both needs and constraints, document what you learn, and then validate it with stakeholders. Setting goals gives the session purpose and direction, so you know what information you’re aiming to gather. Open-ended questions invite stakeholders to describe their workflows, pain points, and desired outcomes in their own terms, uncovering needs that closed questions might miss. Capturing needs and constraints ensures you record functional requirements as well as limitations like budget, regulations, or existing systems that shape the solution. Documenting the results creates a shareable reference you can review and base design decisions on, helping prevent miscommunication. Validating with stakeholders confirms that what you’ve captured reflects their intent, gaining agreement and reducing later rework.

Forcefully pushing pre-made requirements shuts down input and risks building something that doesn’t fit real needs. Yes/no questions provide only a snapshot and miss important context, trade-offs, and constraints. Skipping documentation leaves no trace for accountability or future reference, making scope creep and misalignment more likely.