CAPM Practice: Validate requirements through product delivery

PIRs (also called post-project reviews or benefits reviews) assess whether the delivered solution achieved its business objectives after real-world use. BAs use PIR findings to validate requirements quality and feed insights into future requirements processes.

**Why not B:** Conducting a PIR before implementation begins is contradictory to its purpose. Post-implementation reviews assess the actual outcomes of a delivered solution after it has been in use. Conducting it before implementation would provide no data on whether the solution delivered its expected business benefits.

**Why not C:** Reviewing code against requirements during development describes code review or verification, not a post-implementation review. PIRs occur after the solution has been in production long enough to assess real-world business impact, not during the development phase.

**Why not D:** PIRs are a recognized best practice conducted regularly in professional settings. They provide valuable feedback on whether requirements were correct, solutions delivered expected value, and processes can be improved. Organizations that skip PIRs miss critical learning opportunities for future projects.