CAPM Practice: Validate requirements through product delivery

Passing tests with unsatisfied stakeholders reveals that acceptance criteria were insufficient to capture the full requirements. This is a validation failure — not a development failure. BAs must investigate what the criteria missed and improve requirements processes to prevent recurrence.

**Why not A:** Saying that surveys "don't belong" in product evaluation ignores a key principle of business analysis. Stakeholder satisfaction is a valid and important measure of solution value. Surveys and feedback mechanisms are legitimate tools for assessing whether a delivered feature meets actual user needs beyond technical test criteria.

**Why not B:** Stakeholders should not simply be told to accept a feature that passes technical tests. Passing functional tests confirms the solution works as specified, but it does not guarantee the solution delivers the intended business value or meets stakeholder expectations. The BA should investigate the root cause of dissatisfaction.

**Why not D:** Concluding that the development team performed poorly is premature and misdirected. If the feature passes all defined tests, the development team fulfilled its obligations. The gap likely lies in how requirements were elicited or validated, not in the quality of implementation.