Which Stakeholder Requirements Gathering Technique Matches This Scenario?
Short answer
C Interview
Question
Key Takeaways
The scenario tests recognition of requirements-elicitation methods, with the common trap being the misinterpretation of "freely discuss" as a brainstorming session rather than an open-ended interview.
This question tests the ability to differentiate between stakeholder engagement techniques for requirements elicitation. While candidates split votes due to ambiguous wording, the official guidance prioritizes direct conversational methods like interviews for structured need-gathering.
Common mistake: Brainstorming is frequently selected because the phrase "discuss freely" implies unstructured idea generation, but brainstorming requires specific facilitation rules and focuses on solution generation rather than direct requirement collection.
Expert Analysis
Why the Answer Is Correct
Interviews are the standard technique for directly soliciting stakeholder needs through one-on-one or small-group conversations. The phrase "sits down with them" indicates a dedicated meeting focused on eliciting specific project requirements rather than casual chatter. Even when stakeholders are allowed to speak openly, the underlying structure remains an interview aimed at capturing defined scope elements.Why the Other Options Are Wrong
Process modeling relies on creating flowcharts or diagrams to map system behaviors, which does not match a conversational setup. Brainstorming is a facilitated creativity exercise designed to generate numerous ideas quickly, typically involving larger groups and strict timeboxing. Focus groups require a trained moderator guiding a demographic segment toward specific market or product feedback, differing from the direct requirement-gathering goal described here.Community Comment Notes
Candidates are evenly divided between Brainstorming and Interview due to the question's ambiguous use of "them." Comment [2] accurately points out the poor phrasing regarding group versus individual settings, which fuels the confusion. Comment [3] correctly clarifies that interviews encompass both individual and small-group formats specifically for gathering needs. This split vote highlights how CompTIA sometimes uses overlapping terminology, requiring test-takers to anchor on the primary objective: requirements elicitation.Official Reference
These links open the official vendor documentation in a new tab.
Exam Strategy
Always prioritize the primary objective stated in the scenario when matching techniques to questions. If the goal is explicitly "gathering requirements," default to interviews or surveys unless strong facilitation or creativity cues point elsewhere. Ignore secondary descriptors like "freely discuss" if they contradict the core project management definition of the technique.
Community Votes
50% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
1324c82 👍 3 Answered BB. By allowing stakeholders to freely discuss their ideas and requirements without interruption, the project manager is utilizing the brainstorming technique to gather a broad range of perspectives.
-
044f354 👍 2 Answered CAnother poorly worded complete garbage question. "...the project manager sits down with them..." All at the same time? Or one on one? There is a difference, and it matters. The term "them" leads the reader to perceive that it is a group setting. These question creators need to clearly understand and more effectively translate to the target language. For my answer (C: Interview), I assume each stakeholder is engaged on an individual basis. BUT if it's a group setting, it very well could be a brainstorm or focus group. Good luck out there, folks.
-
fae2322 👍 1 Answered CC. Interview: An interview is a technique where the project manager sits down with stakeholders individually or in small groups to gather their input and discuss their needs and requirements. This allows stakeholders to freely express their thoughts, which is what the scenario describes.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All PK0-005 Questions
Access 102 questions with complete answers and detailed explanations.
View Full PK0-005 Practice Test →