CAPM Practice: Validate requirements through product delivery

Accurate diagnosis drives correct fixes. If requirements were met but the outcome is wrong, improving code won't help — the requirements need revision. If requirements weren't met, the code needs fixing. Misdiagnosing leads to wasted effort solving the wrong problem.

**Why not B:** While both situations result in an unsatisfactory product, the root causes are fundamentally different and require different corrective actions. Distinguishing between the two is critical because a development failure calls for better implementation practices, whereas a requirements failure calls for improved elicitation and validation techniques.

**Why not C:** Post-delivery analysis is absolutely within the BA's responsibility. The BA plays a central role in evaluating whether requirements were correctly specified and whether the delivered solution meets stakeholder needs. This analysis feeds directly into lessons learned and process improvement.

**Why not D:** BAs are well-positioned to determine which type of failure occurred by comparing the delivered solution against both the documented requirements and the actual stakeholder needs. Developers can confirm whether they followed the specification, but the BA is uniquely qualified to assess whether the specification itself was correct.