# Acceptance Criteria

Specific, testable conditions that describe the behavior and outcomes a work item must satisfy to be accepted by product and delivery collaborators.

- Type: practice
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/acceptance-criteria/>)

## What it means

Acceptance criteria are clear conditions used to confirm that a particular story, requirement, or increment behaves as intended. They describe observable outcomes, important rules, boundaries, and error cases for that item. They differ from a team-wide definition of done, which applies common quality expectations across many items.

## Why it matters

Ambiguous work creates mismatched assumptions, late disputes, and fragile testing. Agreeing criteria before implementation gives product, design, engineering, and quality specialists a shared basis for examples and tests. It also protects solution flexibility by specifying required behavior rather than dictating internal construction.

## When to use it

Add acceptance criteria while refining work that is likely to enter delivery soon. They are valuable for user stories, defects, integrations, policy changes, and operational behavior. Keep early ideas lighter until they are prioritized; detailing every distant backlog item creates waste as knowledge changes.

## How it works

1. Discuss the intended outcome, actors, context, business rules, and major risks.
2. Write concise, independently testable statements in language collaborators understand.
3. Cover representative success, boundary, permission, failure, and recovery scenarios.
4. Use examples or Given-When-Then when sequence and context require extra precision.
5. Review criteria with the team and connect them to tests without prescribing unnecessary implementation.

## A practical example

For resetting a password, criteria state that an eligible account receives a time-limited link, the response does not reveal whether an email is registered, an expired link explains how to request another, and successful reset invalidates prior sessions. Each statement can be demonstrated and tested.

## Where it breaks

Criteria cannot enumerate every possible behavior, and long checklists may conceal a poorly framed story. Overly technical wording can constrain design or exclude business collaborators. Passing item-specific criteria also does not guarantee broader qualities such as accessibility, security, maintainability, or product value.

## Common mistakes

- Using subjective terms such as fast, intuitive, or correct without a testable threshold.
- Confusing item-specific acceptance criteria with the team’s definition of done.
- Documenting implementation steps instead of observable behavior and outcomes.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/acceptance-criteria/#visualization-acceptance-criteria>)

## Sources

1. [What Is Acceptance Criteria?](<https://www.atlassian.com/work-management/project-management/acceptance-criteria/>) — Atlassian · Professional guide
2. [Agile Workflow in Azure Boards](<https://learn.microsoft.com/en-us/azure/devops/boards/work-items/guidance/agile-process-workflow?view=azure-devops>) — Microsoft Learn · Technical documentation

## Related topics

- [User Story](<https://wiki.soroush.uk/topic/user-story/>)
- [Backlog Refinement](<https://wiki.soroush.uk/topic/backlog-refinement/>)
- [Product Requirements Document](<https://wiki.soroush.uk/topic/product-requirements-document/>)
