HKSM

A structured set of test plans, cases, scripts, checklists, and results that show how deliverables were examined against requirements. They provide objective evidence of conformance and help identify scope variances that require action.

Key Points

• Includes test plans, test cases, procedures/scripts, inspection checklists, expected results, and actual results/defect logs.
• Traced to requirement IDs and acceptance criteria to show coverage and results at the requirement level.
• Created during quality planning and refined during test execution; maintained under configuration control.
• Provide objective pass/fail evidence to support acceptance, rework, or change decisions.
• Enable visibility into scope completion, gaps, and nonconformities.
• Support audits, stakeholder reviews, and formal sign-offs.

Purpose

Give the team and stakeholders a reliable basis to judge whether the defined scope has been met. They reduce ambiguity by linking tests directly to requirements and recording actual outcomes.

• Verify that deliverables satisfy stated requirements and acceptance criteria.
• Highlight scope variances and defects that threaten acceptance.
• Inform change requests when requirements must be clarified, added, or descoped.
• Support progress reporting by requirement, feature, or work package.

How to Create

• Start from the scope baseline, requirements documentation, acceptance criteria, and quality metrics.
• Derive test scenarios and detailed test cases with clear steps, data, and expected results for each requirement ID.
• Define evaluation methods such as inspections, walkthroughs, sampling plans, measurements, and automated tests.
• Specify entry/exit criteria, environments, tools, roles, and defect severity classification.
• Create inspection and acceptance checklists aligned to the definition of done and stakeholder needs.
• Peer review the package for completeness and traceability; pilot critical tests where feasible.
• Baseline the documents and store them in the configuration-managed repository using organizational templates.

How to Use

• During Monitor and Control Scope, compare actual test results to acceptance criteria to confirm which requirements are fully met.
• Use coverage and pass/fail summaries to detect scope gaps, emerging creep, and areas needing rework.
• Analyze failed tests and defects to assess scope impact and prepare targeted corrective actions.
• Initiate change requests when requirements must be modified or acceptance criteria updated based on findings.
• Update the requirements traceability matrix with latest test status and link to validated deliverables.
• Provide work performance information such as percent complete by requirement or feature.
• In adaptive life cycles, align acceptance tests with the definition of done and review outcomes in iteration reviews.

Ownership & Update Cadence

• Primary owners: QA/Test Lead or Quality Manager; product owner and business representatives review for acceptance criteria.
• Update at each test cycle or iteration, and whenever requirements or acceptance criteria change.
• Maintain version control; significant changes follow integrated change control and are communicated to stakeholders.
• Archive superseded versions and retain execution evidence for compliance and audits.

Example

A team delivering a new checkout module compiles a test plan, 60 detailed test cases mapped to requirement IDs, inspection checklists for UI standards, and a results log.

• Coverage report shows 57/60 requirements tested, 54 passed, 3 failed due to tax calculation and accessibility issues.
• The scope control review uses these results to flag variances, prioritize rework, and raise a change request to refine one ambiguous requirement.
• Traceability and evidence enable clear acceptance of the passed requirements and a plan for the remaining gaps.

PMP Example Question

During a scope control review, stakeholders dispute whether a feature meets its acceptance criteria. What should the project manager consult first to make an objective determination?

1. Quality test and evaluation documents.
2. Project charter.
3. Issue log.
4. Risk register.

Correct Answer: A — Quality test and evaluation documents.

Explanation: These documents contain the test cases, acceptance criteria, and actual results tied to requirements, providing objective evidence for scope decisions. The other documents do not show pass/fail verification against requirements.