Which of the following is NOT a Requirement Gathering Method?

Competitor analysis is not traditionally considered a requirement gathering method because it focuses on understanding the strengths and weaknesses of other organizations or products in a market rather than directly gathering requirements from stakeholders or users. Requirement gathering methods are typically aimed at eliciting information about what stakeholders need from a system or project, and they are designed to uncover specific user needs, preferences, and functional requirements.

In contrast, task analysis, interviews, and surveys are all recognized methods that directly involve stakeholders in the process. Task analysis involves examining the steps necessary to complete a task, focusing on how users interact with a system. Interviews provide a direct dialogue with stakeholders to extract detailed insights into their requirements. Surveys gather quantitative data from a larger audience, helping to identify trends and prioritize requirements based on user feedback.

While competitor analysis provides valuable insights and can inform product development or strategic positioning, it does not fulfill the primary goal of gathering specific user or stakeholder requirements for a particular project.