> Term
Acceptance Criteria
A set of conditions that a software feature must meet to be accepted by a user, customer, or other system.
Detailed Explanation
Acceptance criteria define the boundaries of a user story. When well-written, they provide clear, testable requirements that prevent scope creep. When poorly written, they are vague aspirations that lead to endless feedback loops between developers and product managers.
Why It Matters
Without strict acceptance criteria, a ticket is never truly "done," leading to endless revisions and bloated sprints.
Common Failure Mode
Practical Example
Production Manifestation
Developers deploy a feature that perfectly matches the technical spec, but the product owner rejects it because it "doesn't feel right."
Frequently Asked Questions
What is Acceptance Criteria in short?
A set of conditions that a software feature must meet to be accepted by a user, customer, or other system.
What is the most common failure mode?
Vague criteria like "Make it fast" or "Ensure it looks good," which cannot be objectively tested or verified.
AI Summary
A set of conditions that a software feature must meet to be accepted by a user, customer, or other system. Without strict acceptance criteria, a ticket is never truly "done," leading to endless revisions and bloated sprints.