{"id":294,"date":"2024-12-06T23:39:59","date_gmt":"2024-12-06T23:39:59","guid":{"rendered":"https:\/\/www.mitango.app\/?post_type=definition&p=294"},"modified":"2024-12-06T23:39:59","modified_gmt":"2024-12-06T23:39:59","slug":"acceptance-criteria","status":"publish","type":"definition","link":"https:\/\/www.mitango.app\/fr\/definition\/acceptance-criteria\/","title":{"rendered":"Acceptance criteria"},"content":{"rendered":"

An acceptance criteria is a way to describe the expected behavior from an application.<\/p>\n\n\n\n

Communication is key<\/h2>\n\n\n\n

The acceptance criteria primary role is to communicate.<\/p>\n\n\n\n

That is why they are often written in plain English or pseudo English to make it easier to read for non tech people as it is a great way to share knowledge between the business teams and the engineering ones.<\/p>\n\n\n\n

That way both teams can work autonomously without being blocked by the other one.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

An atomic form<\/h2>\n\n\n\n

As acceptance criterias have to be exhaustive to prevent forgetting a possibility, it is key that each of one them describe only one linear scenario.<\/p>\n\n\n\n

That way it is possible to keep the acceptance criterias simple and less error prone.<\/p>\n\n\n\n

The AAA framework<\/h2>\n\n\n\n

To make it easier to write and verify completeness from an acceptance criteria it is possible to use the AAA framework<\/a>.<\/p>\n\n\n\n

The AAA framework divide acceptance criteria into three steps:<\/p>\n\n\n\n