CAPM Practice: Validate requirements through product delivery

In Scrum, the Product Owner formally accepts or rejects each story at the sprint review by evaluating whether it meets the agreed acceptance criteria. This acceptance is the validation gate — stories that don't meet criteria are returned to the backlog rather than counted as done.

**Why not A:** The product owner does not need external customer sign-off before accepting work in a sprint review. The PO represents the customer and stakeholders and has the authority to accept or reject stories based on acceptance criteria without requiring separate external approval.

**Why not B:** The product owner has a central role in validation during the sprint review. QA validates technical quality, but the PO validates business value by determining whether delivered stories meet acceptance criteria — these are complementary but distinct responsibilities.

**Why not C:** The product owner does not accept all completed work regardless of quality. The PO evaluates each story against its acceptance criteria and rejects stories that do not meet those criteria, returning them to the backlog for further work.