CAPM Practice: Determine how to gather requirements

Brainstorming encourages uninhibited idea generation by deferring evaluation — all ideas are recorded without judgment. This frees participants to suggest unusual ideas that can spark creative solutions, surfacing requirements that more structured approaches might miss.

**Why not A:** Brainstorming is a divergent thinking technique focused on generating ideas, not a structured method for ranking or prioritizing requirements. Prioritization techniques such as MoSCoW, weighted scoring, or analytic hierarchy process are used after ideas have been gathered. Brainstorming deliberately avoids evaluation during the idea-generation phase.

**Why not B:** Brainstorming is a group activity, not a one-on-one interview technique. Its power comes from building on others' ideas in a collaborative setting. Individual interviews serve a different purpose and use structured or semi-structured questioning rather than free-form idea generation.

**Why not C:** Thinking aloud while using a system describes usability testing or think-aloud protocol, not brainstorming. That technique evaluates an existing system or prototype. Brainstorming occurs earlier in the process to generate new ideas and possibilities before any solution is built.