Difference between revisions of "Acceptance criteria"
(→Related lectures) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Acceptance criteria]] (hereinafter, the ''Criteria'') is the specification for a set of conditions that the [[ | + | [[Acceptance criteria]] (hereinafter, the ''Criteria'') is the specification for a set of conditions that the [[market exchangeable]] 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 ''Criteria''; otherwise, it fails. |
| + | |||
==Definitions== | ==Definitions== | ||
Latest revision as of 13:08, 6 May 2023
Acceptance criteria (hereinafter, the Criteria) is the specification for a set of conditions that the market exchangeable 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 Criteria; otherwise, it fails.
Definitions
According to the BABOK Guide (3rd edition),
- Acceptance criteria. Criteria associated with requirements, products, or the delivery cycle that must be met in order to achieve stakeholder acceptance.
According to the ITIL Foundation 4e by Axelos,
- Acceptance criteria. A list of minimum requirements that a service or service component must meet for it to be acceptable to key stakeholders.
Test
- Main wikipage: Acceptance test
Acceptance test is the derivative from the Criteria that verifies whether a feature is functional. The test has only two results: pass or fail. The Criteria usually include one or more acceptance tests.
Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.
