CAPM Practice: Determine how to gather requirements

Requirements sign-off creates a formal baseline — stakeholders explicitly agree that requirements correctly represent their needs. This prevents rework from scope disputes later and establishes accountability for both parties: stakeholders approved requirements; the team will deliver them.

**Why not A:** The project manager signing the requirements document as author describes document authorship, not requirements sign-off. Sign-off is a stakeholder approval action where business stakeholders confirm that the documented requirements accurately represent their needs and agree to proceed on that basis.

**Why not B:** Requirements sign-off is not a legal signature required by regulatory bodies in most cases. While regulated industries may have specific approval requirements, requirements sign-off is fundamentally a project governance practice for establishing shared commitment and a requirements baseline.

**Why not C:** The BA signing off on their own work product describes self-review, not requirements sign-off. Sign-off involves stakeholders who provided the requirements confirming that the documented version is accurate and complete, establishing mutual accountability for what will be built.