Articles → PROJECT MANAGEMENT → Acceptance Criteria In Agile

Acceptance Criteria In Agile

This article describes the Acceptance criteria in Agile.

Different Ways Of Writing The Acceptance Criteria

There are two ways of writing the acceptance criteria: -

Given-When-Then Format
Checklist Format

Given-When-Then Format

This format follows a structured approach to defining scenarios: -

Given - Pre-conditions or context

When - Action or trigger.

Then - Expected outcome or result.

Let us say we are defining acceptance criteria for a login feature.

#### Scenario: Successful login
Given - A registered user with valid credentials.
When - The user enters a valid username and password and clicks the login button.
Then - The user is redirected to the dashboard page.


#### Scenario: Invalid login attempt
Given - A user on the login page.
When - The user enters an invalid username or password.
Then - An error message is displayed indicating invalid credentials.

Checklist Format

The checklist format uses bullet points or a numbered list for each acceptance condition. It is more straightforward and lists requirements.

Checklist
The user should be able to log in with valid credentials successfully.
An error message should be shown when invalid credentials are entered.
The "Remember Me" option should save the username for future logins.
The user should be redirected to the dashboard after a successful login.
The user should be blocked after 3 consecutive failed login attempts.

Which Way To Choose?

The given-when-then format is preferred when working with complex scenarios that involve different states and actions. The checklist format is preferred for simpler features or when listing straightforward conditions without needing detailed flow descriptions.

Posted By -	Karan Gupta

Posted On -	Monday, October 28, 2024

Query/Feedback

Your Email Id		**

Subject		*

Query/Feedback	Characters remaining 250	**