Product Backlog items have the attributes of a description, order, estimate, and value. Since it is the PO's responsibility to ensure that everyone fully understands the story why would defining the way that you know the story has been satisfied be a problem? I feel that the PO should provide acceptance criteria as part of the story definition.įrom the Scrum Guide (emphasis added by me) PO must not define and specify the acceptance criteria? Think Definition of "Done" at the macro level, and Acceptance Criteria at the micro.
Acceptance Criteria: The password must be no less than 8 and no greater than 12 characters, contain at least one Uppercase letter, one lower case letter, and at least one number.
Definition of "Done": No Critical and High defect will be accepted code coverage percentage to be at least 70% all web pages to load in under 2 seconds.What often confuses people is this statement: Product Backlog items often include test descriptions that will prove its completeness when "Done".Īcceptance criteria, which is optional and a complimentary Scrum practice taken from XP, may apply to the Product Backlog items, and is in the context to the desired functionality of the Product Backlog items. You won't find anything about Acceptance Criteria in the Scrum Guide. There is a myth that the Definition of "Done" is applied to multiple levels. The short answer is that the Definition of "Done" applies to the entire product Increment, and does not apply to a Product Backlog item (or Epic/Feature/Story).