Study guides / CAPM: Certified Associate in Project Management / Validation, traceability & acceptance
Validation, traceability & acceptance
CAPM: Certified Associate in Project Management · quick review
Making sure the right thing gets built and accepted: traceability, verification versus validation, acceptance criteria and solution evaluation.
The rules
- The requirements traceability matrix links each requirement back to its business objective and forward to design, build and test, so nothing is lost or added unnoticed.
- Verification: does the solution meet the specification? (built right). Validation: does it meet the real need? (built the right thing).
- Acceptance criteria define when a requirement or story is satisfied; user acceptance testing confirms it with the people who'll use it.
- Solution evaluation after delivery checks whether the expected benefits are being realized, often against the benefits management plan.
- Requirement changes go through change control (predictive) or backlog refinement (adaptive), and the traceability matrix is updated.
Common traps
- Passing every test against the spec doesn't prove users' needs are met.
- A requirement with no business objective traced to it may be gold plating.
How it's tested
Distinguishing verification from validation, and using traceability to find missing or unnecessary requirements.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson