CAPM Practice: Validate requirements through product delivery

Meeting requirements but missing outcomes reveals a fundamental requirements quality failure. Requirements were a means to an end — if meeting them doesn't achieve the end, the requirements were wrong. BAs must investigate the gap to understand what requirements would actually produce the desired outcome.

**Why not A:** The development team built what was specified in the requirements. If the requirements themselves were flawed, holding the development team accountable for the business outcome is unfair and misdirected. The root cause lies in requirements quality, not implementation quality.

**Why not C:** Closing the project because requirements were met ignores the fundamental purpose of the project — achieving business outcomes. Meeting requirements is a means to an end, and if the end was not achieved, the project cannot be considered successful just because specifications were followed.

**Why not D:** Defining project success solely by requirements compliance ignores the ultimate purpose of requirements: delivering business value. A project that meets every specification but fails to improve the business has a requirements quality problem that must be investigated and addressed.