Which are three requirement gathering methods?

• A. Task Analysis, Interviews, Surveys
• B. Brainstorming, Radar diagrams, Focus groups
• C. Ethnography, Card sorting, Use cases
• D. Interviews, Surveys, Focus groups

Answer: (A)

When gathering requirements, you want methods that directly uncover what users need and how they will work with the system. Task analysis excels at revealing the concrete actions users perform, the steps involved, and the data and decisions each task requires. This anchors what the system must support in real workflows, making functional requirements much clearer.

Interviews provide deep, contextual insights from stakeholders and domain experts. They let you probe expectations, constraints, and priorities, and they help uncover needs that aren’t visible in artifacts or documents.

Surveys extend those insights to a larger group, giving you scalable data to validate findings, quantify preferences, and rank requirements by importance or frequency.

Other options mix techniques that are not as directly focused on eliciting user needs as primary methods. For example, brainstorming is more about generating ideas, radar diagrams are visualization tools, and ethnography, card sorting, or use cases each address different aspects like observation, information architecture, or modeling rather than straightforward requirement elicitation. Focus groups can be useful, but the trio of task analysis, interviews, and surveys provides a balanced, direct approach to uncovering and validating requirements across both depth and breadth.