Acceptance Condition Verification

Acceptance Condition Verification is the deliberate act, performed during and at the conclusion of execution, of checking a completed work item against its confirmed acceptance criteria to determine objectively whether it genuinely satisfies what was agreed upon, rather than relying on a subjective impression that the work is likely finished. It transforms acceptance criteria from a planning-time artifact into an active, execution-time gate that must be explicitly and honestly passed before an item can be considered truly done.

Why Verification Is a Distinct Step From Having Criteria

Criteria Existing Is Not the Same as Criteria Being Checked

An item can carry well-written, confirmed acceptance criteria from planning while never being explicitly verified against them during execution, leaving open the possibility that completed work diverges from what was actually agreed without anyone noticing until later.

Self-Assessment Alone Is Prone to Bias

A contributor who has been immersed in building a piece of work is naturally inclined to view it favorably; explicit, deliberate verification against the original criteria provides a more objective check than relying solely on the builder's own sense that the work is finished.

Verification Closes the Loop Opened During Planning

Acceptance criteria confirmed during planning represent a commitment about what will be delivered; verification is the corresponding execution-time act that confirms that commitment was actually fulfilled, completing the loop between intention and outcome.

What Verification Involves

Systematic Criterion-by-Criterion Checking

Rather than a general impression of completeness, verification works through each specific acceptance criterion individually, confirming that the finished work genuinely satisfies it rather than approximately or partially meeting it.

Testing Against Concrete Scenarios

Applying the finished work to the same specific examples and edge cases discussed during acceptance criteria confirmation provides concrete evidence of whether the criteria are truly met, rather than relying on abstract judgment alone.

Independent Verification Where Appropriate

Having someone other than the original contributor perform or participate in verification introduces a valuable independent perspective, reducing the risk that assumptions made during building go unexamined.

Documentation of Verification Outcomes

Recording the results of verification, including any criteria found not to be satisfied, provides a clear, traceable record of the item's actual state rather than relying on informal or undocumented confirmation.

When Verification Occurs

Continuous Verification During Execution

For complex items, verification may occur incrementally as different aspects of the acceptance criteria are addressed, rather than being deferred entirely until the item appears complete.

Final Verification Before Marking Complete

A conclusive verification pass, checking the finished item against the full set of acceptance criteria, occurs before the item is formally marked as done, serving as the final gate before completion is declared.

Verification During Review Activities

Formal review points, such as code review or a demonstration to stakeholders, often incorporate acceptance condition verification as part of their broader evaluation of the completed work.

Consequences of Weak Verification Practice

Silent Divergence Between Intent and Outcome

Without deliberate verification, completed work can drift from what was actually agreed without anyone realizing until a later stage, such as stakeholder review or production use, when correction becomes more costly.

Inflated Sense of Completion

Marking items as done based on informal impression rather than genuine verification against criteria can create an inaccurate picture of true progress, distorting forecasts and stakeholder expectations.

Erosion of Trust in the Definition of Done

If items marked complete are later found not to genuinely satisfy their acceptance criteria, trust in the team's completion signals erodes, requiring greater external scrutiny that undermines efficient collaboration.

Measuring Verification Effectiveness

Post-Completion Criterion Failure Rate

A high rate suggests that verification during execution is insufficiently rigorous, allowing gaps to surface only after completion has already been declared.

Common Failure Modes

Treating Verification as a Formality

Performing a cursory glance at completed work rather than genuinely checking it against each specific acceptance criterion undermines the entire purpose of having explicit criteria in the first place.

Relying Solely on the Original Contributor's Judgment

Allowing only the person who built the work to also be the sole judge of whether it meets acceptance criteria removes the benefit of independent perspective that verification is meant to provide.

Skipping Verification Under Time Pressure

Rushing to mark items complete near the end of an iteration or delivery period, without adequate verification, risks discovering unmet criteria only after the fact, when correction is more disruptive.

Verifying Against Outdated Criteria

Checking completed work against acceptance criteria that were never updated despite legitimate changes discovered during execution can produce a verification result that is technically passed but practically meaningless.