CAPM Practice: Determine how to gather requirements

Requirements documentation serves multiple purposes: preserving agreed-upon requirements, enabling review and sign-off, providing implementation guidance for the team, supporting testing, and managing future changes against a baseline.

**Why not B:** Requirements documentation does not aim to replace verbal communication or reduce meetings. Verbal discussions remain essential for elicitation and clarification. Documentation supplements conversation by preserving agreed-upon requirements in a reviewable format.

**Why not C:** While documentation can serve as a historical record, its primary purpose is not legal liability protection. The core function is enabling stakeholders to review requirements and giving the team clear implementation guidance.

**Why not D:** Although regulatory compliance may require documentation in some industries, the primary purpose of requirements documentation is to capture and communicate requirements for review and implementation — not merely to satisfy external regulatory mandates.