© 2019 by DevelopAgile.com 🐿️

Website developed through ongoing iterative and agile development.

PSST! Need some help?

You can search for terms in the Search bar above! ;)

The Agile Dictionary

 

There are different definitions of the acceptance criteria but we will make it simple.

This is defined by Google as“Pre-established standards or requirements a product or project must meet.” and by Microsoft Press as “conditions that a software product must satisfy to be accepted by a user, customer or other stakeholders.”

It is a set of statements detailing a user story that will be tested once coded/developed to check if the feature is in accordance with the user needs. Acceptance criteria state the intent of the user (What) and not the solution (How). These are pass/fail tests that can specify both functional and non-functional requirements; there is no partial acceptance : the criterion is either met or not met. We recommend to use the Given/When/Then format as it makes acceptance criteria easy to understand and consistent.

Ideally, the acceptance tests are subsequently automated by the developers so that they can easily run on all iterations of the software, ensuring that the accepted feature has not been broken by newer code.

Acceptance Criteria

Related Terms:

Definition of Done

Antipatterns are solutions aiming to solve a problem or improve things but actually, end up as ineffective or even result in undesired consequences.

Antipattern

Artifacts are tangible by-products during product development. There are three primary artifacts according to Scrum : the Product Backlog, the Sprint Backlog and the Product Increment. Artifacts are designed to increase transparency of information in the Team and make sure everyone has the same understanding.

Artifacts