Who writes acceptance criteria?

Typically the Product Owner or client, with input from the development team. At Bookuvai, our AI PM drafts criteria and the client reviews and approves them.

How many acceptance criteria per story?

Usually 3–8. Fewer suggests the story is too vague; more suggests it should be split into multiple stories.

Acceptance Criteria Explained

The specific, testable conditions that define when a feature or milestone is truly complete.

Acceptance Criteria

A set of predefined conditions that a deliverable must satisfy to be considered complete and accepted by the client or Product Owner.

Explanation

Acceptance criteria remove ambiguity from requirements. Instead of "the login should work well," acceptance criteria specify: "Given a registered user, when they enter valid credentials and click Login, then they are redirected to the dashboard within 2 seconds." They can be written in Given/When/Then (Gherkin) format or as simple checklists. Every user story and milestone should have acceptance criteria defined before development begins.

Bookuvai Implementation

Every Bookuvai milestone includes detailed acceptance criteria co-authored by the AI PM and the client during the discovery phase. These criteria are displayed in the milestone review interface, and each must be checked off during the approval process. This ensures there is no ambiguity about what "done" means.

Key Facts

Defined before development begins
Must be testable and measurable
Serve as the basis for QA testing

Related Terms

Frequently Asked Questions

Who writes acceptance criteria?: Typically the Product Owner or client, with input from the development team. At Bookuvai, our AI PM drafts criteria and the client reviews and approves them.
How many acceptance criteria per story?: Usually 3–8. Fewer suggests the story is too vague; more suggests it should be split into multiple stories.