CAPM Practice: Determine how to gather requirements

Mind maps radiate branches from a central topic, visually organizing and connecting related concepts. BAs use them during brainstorming and requirements analysis to explore a problem space, identify categories, and find gaps in requirements coverage.

**Why not A:** This is a play on words that has no basis in actual BA practice. Mind mapping is not about assigning or "mapping" requirements to individual team members' minds. It is a visual brainstorming and structuring technique used to explore ideas and their relationships.

**Why not B:** Mind mapping is a diagramming technique, not a psychological profiling method. While understanding stakeholder motivations is important in business analysis, mind mapping focuses on visually organizing and connecting concepts, not on analyzing personalities or psychological profiles.

**Why not C:** Mind mapping does not depict a sequence of meetings or a review schedule. It is a non-linear, radial diagram that branches outward from a central concept. Confusing it with a meeting timeline misrepresents both its structure and its purpose in requirements gathering.