According to the PMBOK Guide, specifically within the Collect Requirements process, the Delphi Technique is a specific group creativity technique (and a form of expert judgment) used to reach a consensus among a group of experts.
* Process and Methodology: In the Delphi technique, a facilitator uses a questionnaire to solicit ideas about the project requirements from a selected group of experts. The responses are summarized and then recirculated to the experts for further comment.
* Anonymity: A key characteristic of this technique is that the experts participate anonymously. This prevents any single participant from unduly influencing the others (the " bandwagon effect " ) and encourages honest, unbiased feedback.
* Iterative Rounds: The process typically involves several rounds of questionnaires and feedback until a consensus is reached. This is highly effective for reducing bias in the data and ensuring that the requirements are not skewed by a dominant personality in a face-to-face setting.
Analysis of other choices:
* Choice B (Nominal group technique): This technique enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization. It usually involves face- to-face interaction or direct collaboration.
* Choice C (Affinity diagram): This is a tool used to allow a large number of ideas to be classified into groups for review and analysis. It is a categorization tool, not a feedback/consensus-gathering method.
* Choice D (Brainstorming): This is a general technique used to generate and collect multiple ideas related to project and product requirements. It lacks the formal, iterative, and anonymous structure of the Delphi technique.