CAPM Practice: Determine how to gather requirements

Requirements completeness is never guaranteed, but triangulation helps: multiple elicitation techniques surface different aspects; diverse stakeholders cover different perspectives; tracing requirements to business goals identifies gaps; reviews catch missed items.

**Why not A:** Waiting until development reveals missing requirements is a reactive approach that leads to costly rework and schedule delays. The BA should proactively verify completeness before development begins rather than relying on the development process to expose gaps.

**Why not B:** Having the project manager review requirements is helpful but insufficient. The PM typically lacks the domain expertise and stakeholder relationships needed to assess whether all business needs have been captured. Completeness verification requires multiple techniques and diverse perspectives.

**Why not D:** Counting requirements against industry benchmarks is not a meaningful measure of completeness. Every project has unique business needs, so the number of requirements varies greatly. A project could have more requirements than a benchmark yet still be missing critical ones.