CAPM Practice: Determine how to gather requirements

Hidden requirements are invisible to stakeholders because they're assumed, forgotten, or unknown. BAs uncover them by: leveraging domain knowledge to anticipate unstated needs, studying similar systems for typical requirements, probing 'what happens if...' scenarios, and using diverse elicitation techniques that reach beyond stated preferences.

**Why not A:** Requirements added secretly by developers without BA approval describes unauthorized scope changes or gold-plating, not hidden requirements. Hidden requirements are needs that stakeholders themselves did not articulate because they assumed them, forgot them, or did not know to ask for them.

**Why not B:** Requirements kept confidential from the development team describes a communication or access control issue, not hidden requirements. Hidden requirements are invisible because they exist in stakeholders' unstated assumptions, not because someone is intentionally withholding information.

**Why not C:** Requirements stored in hidden sections of documents describes a document organization problem, not hidden requirements in the BA sense. Hidden requirements refer to genuine stakeholder needs that were never documented because they were assumed, overlooked, or not yet recognized.