Difference between revisions of "Acceptance criteria"
(Created page with "Acceptance criteria is the specification for a set of conditions that the product must meet in order to satisfy the customer. In Agile methodology, the product o...") |
|||
| Line 1: | Line 1: | ||
[[Acceptance criteria]] is the specification for a set of conditions that the [[product]] must meet in order to satisfy the customer. In [[Agile methodology]], the [[product owner]] writes statements from the customer's point of view that explain how a [[user story]] or feature should work. In order for the story or feature to be accepted it needs to pass the acceptance criteria; otherwise, it fails. | [[Acceptance criteria]] is the specification for a set of conditions that the [[product]] must meet in order to satisfy the customer. In [[Agile methodology]], the [[product owner]] writes statements from the customer's point of view that explain how a [[user story]] or feature should work. In order for the story or feature to be accepted it needs to pass the acceptance criteria; otherwise, it fails. | ||
| + | |||
| + | |||
| + | ==Related coursework== | ||
| + | *[[Business Analysis Quarter]]. | ||
| + | |||
| + | [[Category: Septem Artes Administrativi]][[Category: Articles]] | ||
Revision as of 00:57, 29 December 2018
Acceptance criteria is the specification for a set of conditions that the product must meet in order to satisfy the customer. In Agile methodology, the product owner writes statements from the customer's point of view that explain how a user story or feature should work. In order for the story or feature to be accepted it needs to pass the acceptance criteria; otherwise, it fails.
