Business Analysis Frameworks · Topic 4 of 4
Validating Requirements Through Product Delivery
CAPM requirement validation: writing acceptance criteria, verification versus validation, and using the traceability matrix or backlog to judge readiness.
- 3 min
- Acceptance criteria: specific, testable, agreed up front; Given / When / Then.
- Verification: built right, against specifications. Validation: right thing, against needs.
- Validate scope is formal acceptance of deliverables in predictive projects.
What it is
Validating requirements means confirming that what is delivered actually meets the stakeholders' needs. The main tools are acceptance criteria, which define what "acceptable" means for each requirement, and the requirements traceability matrix or product backlog, which show whether every needed requirement has been built, tested and accepted.
How it works
Acceptance criteria
Acceptance criteria are the conditions a requirement or story must meet to be accepted by the stakeholder. Good criteria are:
- Specific and testable, with a clear pass or fail.
- Agreed before the work starts, so everyone knows the target.
- Written from the user's point of view.
A common format is Given / When / Then:
| Part | Example |
|---|---|
| Given a context | Given a customer with items in the cart |
| When an action happens | When they enter a valid card and press Pay |
| Then an outcome is expected | Then the order is confirmed and a receipt is emailed |
When the situation changes, for example a new regulation or feedback from users, the acceptance criteria may need to change too. The change is agreed with the stakeholders, and in predictive projects it goes through change control.
Verification versus validation
| Verification | Validation | |
|---|---|---|
| Question | Did we build it right? | Did we build the right thing? |
| Checks | The product meets the specification and quality standards | The product meets the stakeholders' real needs |
| Typical activity | Inspection, testing against specs, quality control | Demonstration, user acceptance testing, stakeholder review |
In predictive projects, validate scope is the formal acceptance of completed deliverables by the customer or sponsor, usually after quality control has verified them.
Is the product ready for delivery?
| Approach | How readiness is judged |
|---|---|
| Predictive | The RTM shows each in-scope requirement linked to a completed deliverable, a passed test and formal acceptance. Gaps mean the product is not ready |
| Adaptive | The product backlog shows which items meet their acceptance criteria and the Definition of Done. The product owner decides whether the done items make a releasable increment |
A worked example: before go-live, the BA reviews the RTM. Ninety-five requirements show "passed and accepted", but three security requirements show "test failed". The product is not ready; the failed items must be fixed and retested, or the stakeholders must formally agree a change.
User acceptance testing
User acceptance testing (UAT) is testing by real users or their representatives to confirm the solution works for them in realistic conditions. It is a key validation activity before release.
"Built to spec" is verification. "Meets the user's need" is validation. Exam questions often hinge on this difference.
How the exam asks about this
- "Which question does validation answer?" Did we build the right thing?
- "How can the BA check that every requirement has been tested and accepted?" Using the requirements traceability matrix.
- "When should acceptance criteria be defined?" Before the work starts, agreed with stakeholders.
What to remember for the exam
- Acceptance criteria: specific, testable, agreed up front; Given / When / Then.
- Verification: built right, against specifications. Validation: right thing, against needs.
- Validate scope is formal acceptance of deliverables in predictive projects.
- Readiness: RTM complete in predictive; backlog items done and accepted in adaptive.
- UAT confirms the solution works for real users.
Passing internal tests does not mean the stakeholder accepts the product. Validation needs the stakeholder's confirmation.
Common mistakes
Writing acceptance criteria after the work is done. Define them first.
Using verification and validation as synonyms. They answer different questions.
Releasing with failed requirements unnoticed. Check the RTM or backlog before delivery.
Check yourself
What is the difference between verification and validation?
Verification checks the product was built right against its specification; validation checks it is the right product for the stakeholders' needs.
What format is often used for acceptance criteria?
Given / When / Then.
How does the RTM help decide if a product is ready for delivery?
It shows whether every requirement is linked to a completed deliverable, a passed test and acceptance.
Topic 4 of 4 in Business Analysis Frameworks
Test yourself on Business Analysis Frameworks
The full PMI CAPM question bank has 1,049 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by PMI. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.