CAPM Practice: Validate requirements through product delivery

Minimum viable validation balances quality confidence with delivery speed. Exhaustive testing of every edge case isn't always warranted — the BA and team determine the level of validation sufficient to make a confident delivery decision, proportionate to the risk of requirements errors in that context.

**Why not A:** Minimum viable validation is not about validating the fewest requirements to keep stakeholders satisfied. It is about defining the right level of validation effort that provides sufficient confidence proportionate to the risk, ensuring quality without over-investing in low-risk areas.

**Why not B:** Performing only automated testing with no human validation is incomplete. Minimum viable validation includes the appropriate mix of automated and human validation. Some requirements can only be validated through human judgment, and eliminating human validation creates blind spots.

**Why not D:** Accepting delivery without validation to maximize speed is not minimum viable validation — it is no validation. Minimum viable validation deliberately determines the smallest sufficient effort to make an informed, confident delivery decision, not the elimination of validation entirely.