CAPM Practice: Determine how to conduct stakeholder communication

Requirements reviews bring stakeholders and technical experts together to examine requirements before development starts. They catch errors and ambiguities while changes are still cheap, and build stakeholder understanding and buy-in.

**Why not A:** A post-project review of whether requirements were met is a retrospective or benefits assessment activity, not a requirements review. Requirements review occurs before development begins, specifically to catch errors, gaps, and ambiguities while they are still inexpensive to fix.

**Why not C:** An automated tool that checks documents for completeness describes requirements validation tooling, not a requirements review. A review is a structured human examination involving stakeholders and subject matter experts who apply domain knowledge to evaluate quality — something automated tools cannot fully replicate.

**Why not D:** A project manager's annual performance review of a BA is a human resources activity, not a communication mechanism. Requirements review is a technique for examining requirements artifacts, not for evaluating the people who create them.