Acceptance Criteria
Acceptance Criteria are results people can see and test. They say when a feature works well enough to accept.
Another example
When saving, the page shows progress and keeps data after refresh. It also explains data or network errors.
Main parts
- 01Preconditions
- 02Observable expected behavior
- 03Edge cases and failure behavior
Use it when
Write them before coding so product, design, engineering, and QA agree on the same result.
Do not use it when
Never use a personal opinion such as “looks premium.” Write a result another person can check.
Name used in code
Given / When / Then Before you ship
Check the target user, wanted result, current baseline, evidence source, scope, owner, and success level. List assumptions, open risks, and the next test or decision.
Outcome: Use Acceptance Criteria to make a focused product decision backed by evidence. User context: When saving, the page shows progress and keeps data after refresh. It also explains data or network errors. Product concept to apply: Acceptance Criteria. Why it fits: Write them before coding so product, design, engineering, and QA agree on the same result. Do not use it when: Never use a personal opinion such as “looks premium.” Write a result another person can check. Product framing: Name the target user and wanted result. Record the current baseline and evidence. Set what is in and out of scope, the limits, the owner, and the time frame. Decision quality: Keep facts, guesses, and unknowns separate. Record the options you did not choose and what evidence would change the decision. Acceptance criteria: The document names an owner, target user, measurable result, scope limit, evidence source, open risks, and next test. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Target group, baseline, success level, owner, time frame, dependencies, and review schedule.
Check this request
Review the current use of Acceptance Criteria. Definition: Acceptance Criteria are results people can see and test. They say when a feature works well enough to accept. Release checks: Check the target user, wanted result, current baseline, evidence source, scope, owner, and success level. List assumptions, open risks, and the next test or decision. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.