CAPM Practice: Validate requirements through product delivery

Requirements quality directly determines QA effectiveness. Clear, testable acceptance criteria enable QA to write precise test cases. Ambiguous requirements produce ambiguous tests that miss real defects or flag false failures. BAs who write high-quality acceptance criteria enable effective QA validation.

**Why not A:** Claiming that "QA replaces the need for requirements validation" fundamentally misunderstands both disciplines. Quality assurance focuses on process adherence and defect prevention, while requirements validation ensures that the right requirements have been identified and accurately reflect stakeholder needs. Both activities are necessary and complementary, not substitutes for one another.

**Why not B:** Stating that QA and requirements validation are "completely separate with no overlap" ignores the important relationship between these activities. QA processes often leverage validated requirements as the basis for test cases and quality criteria. The two disciplines inform and strengthen each other throughout the project lifecycle.

**Why not D:** Asserting that "only QA teams can validate requirements" incorrectly limits validation responsibility. Requirements validation is primarily a business analysis activity that involves stakeholders, subject matter experts, and the BA team. While QA professionals may participate in validation reviews, they are not the sole owners of this activity.