Tiêu chí Chấp nhận
Điều kiện cụ thể mà một user story hoặc requirement phải đáp ứng để được chấp nhận.
Acceptance Criteria are clear, testable conditions that a feature or user story must meet to be considered “done.”
In short:
Acceptance Criteria = How we know this works correctly
Acceptance Criteria are specific rules that define when a user story is acceptable to the Product Owner.
If all acceptance criteria are met → the story is accepted.
They help:
Avoid misunderstandings between business & developers
Define scope clearly (what’s in / what’s out)
Make testing objective (pass / fail)
Prevent “almost done” features
Written under each User Story
Used by:
Developers (to build correctly)
QA/Testers (to test)
Product Owner (to accept or reject)
User Story
As a salesperson, I want to add a new product so that I can sell it to customers.
Acceptance Criteria
Product name is required
Price must be greater than 0
Category must be selectable from a list
Product is saved successfully
Product appears in product list after saving
Clear
Easy to read
Example:
User must be logged in
Required fields show validation errors
Data is saved correctly
This format is very clear and testable.
Example:
Given the user is logged inWhen the user submits the product form with valid dataThen the product is saved and shown in the product listGood Acceptance Criteria should be:
Clear – no ambiguity
Testable – can be verified
Specific – no vague words like “fast”, “nice”
Focused on behavior, not implementation
❌ Bad:
“The system should load quickly”
✅ Good:
“The product list loads within 2 seconds for up to 1,000 products”
Acceptance Criteria
Definition of Done
Story-specific
Applies to all stories
What the feature must do
What “done” means globally
Owned by Product Owner
Owned by Team
User Story
As a salesperson, I want to see recommended furniture for a customer so I can upsell better.
Acceptance Criteria
Recommendations are based on customer purchase history
At least 3 products are suggested
Recommended products are in stock
Salesperson can add a recommended product to the order in 1 click
Acceptance Criteria = conditions to accept a story
They make work clear, measurable, and testable
Every important user story should have them
If you want, I can:
Help you write Acceptance Criteria for your current backlog
Review your existing stories and improve them
Show real-world examples for AI features in your product
Just tell me what you’re working on next 🚀
