CAPM Practice: Validate requirements through product delivery

Missed requirements after delivery require two responses: (1) tactical — add the requirement to the backlog for prioritization and delivery; (2) strategic — investigate why it was missed to prevent recurrence. Root cause analysis (insufficient stakeholder coverage? wrong elicitation technique?) improves future requirements quality.

**Why not B:** Blaming stakeholders is unprofessional and counterproductive. Elicitation is a shared responsibility, and the BA is accountable for using techniques that uncover needs effectively. Shifting blame damages trust and does nothing to address the gap or prevent similar oversights in the future.

**Why not C:** Simply documenting a lesson learned without taking corrective action leaves the user need unaddressed. While lessons learned are valuable, the immediate priority is to add the missing requirement to the backlog so it can be delivered, alongside improving processes to prevent recurrence.

**Why not D:** Accepting missed requirements as inevitable without any response is a passive and negligent approach. While no elicitation process is perfect, a professional BA takes concrete steps to address discovered gaps, understand their root cause, and strengthen future requirements gathering practices.