CAPM Practice: Validate requirements through product delivery

Systematic documentation of validation failures improves requirements practice. Root cause patterns (unclear acceptance criteria → failed stories; missing stakeholder → missed requirements) reveal systematic problems. Tracking these patterns and responding with process improvements continuously elevates requirements quality.

**Why not B:** Keeping validation failure lessons confidential to protect team morale is counterproductive. Documenting lessons learned—including failures—creates organizational knowledge that prevents the same mistakes from recurring. A healthy project culture treats failures as learning opportunities, and suppressing this information deprives future projects of valuable insights.

**Why not C:** Documenting validation failures is not solely the quality assurance team's responsibility. The business analyst plays a key role in capturing lessons related to requirements quality, stakeholder engagement, and validation approach effectiveness. Lessons learned is a shared responsibility that benefits from multiple perspectives across the project team.

**Why not D:** Lessons learned should not be documented only when there are complete project failures. Partial failures, near-misses, and even minor validation issues all provide valuable learning opportunities. Waiting for catastrophic failure means missing the chance to capture incremental improvements that could prevent larger problems on future initiatives.