Acceptance Criteria and Requirements Validation

Requirements validation ensures that the project delivers what stakeholders actually need. This is Domain 4, Task 6: Validate requirements through product delivery.

Validation vs. Verification

Memory Aid: Validation = Value to the customer. Verification = Verifying against specifications.

---

Acceptance Criteria

Acceptance criteria are the specific conditions that a product, service, or result must satisfy to be accepted by the customer or stakeholder.

Characteristics of Good Acceptance Criteria

Acceptance Criteria Formats

Given-When-Then (Gherkin Format)

Used primarily in agile for behavior-driven development:

• Given [precondition/context]
• When [action/trigger]
• Then [expected outcome]

Example:

• Given a registered user is on the login page
• When they enter valid credentials and click "Login"
• Then they are redirected to their dashboard within 2 seconds

Checklist Format

Simple list of conditions that must be met:

• User can log in with email and password
• Failed login shows error message after 3 attempts
• Password must be at least 8 characters
• Login session expires after 30 minutes of inactivity

Rule-Based Format

Business rules that define behavior:

• If order total exceeds $50, free shipping applies
• If payment fails, order status changes to "pending"
• If user is inactive for 90 days, account requires reactivation

---

User Acceptance Testing (UAT)

User Acceptance Testing is the final testing phase where end users verify that the solution meets their actual needs in a real-world context.

UAT Process

1. Define UAT plan — Scope, schedule, participants, success criteria
2. Create test scenarios — Based on acceptance criteria and real-world use cases
3. Prepare test environment — Set up a realistic testing environment
4. Execute tests — End users perform tests following scenarios
5. Document results — Record pass/fail for each scenario, log defects
6. Decision — Accept, accept with conditions, or reject the deliverable

UAT vs. Other Testing Types

---

Validation Through the Project Life Cycle

Validation should occur continuously, not just at the end:

Predictive Validation Points

Agile Validation Points

---

Readiness Assessment

Before delivery, the BA or project team should assess readiness using the RTM or product backlog:

Readiness Checklist

• All acceptance criteria are defined and agreed upon
• All required testing is complete and passed
• All critical defects are resolved
• Training materials are prepared (if applicable)
• Transition plan is in place (data migration, cutover)
• Stakeholders have signed off on acceptance
• Support processes are ready
• Documentation is complete

Using the RTM for Readiness

The RTM can serve as a readiness checklist by verifying:

• All requirements have associated test cases
• All test cases have been executed
• All required test cases have passed
• All requirements are marked as complete
• Traceability is maintained from business need to verified deliverable