Agile Business Analysis Acceptance Criteria and Definition of Done

Question 1

What is the primary purpose of acceptance criteria in Agile Business Analysis?

Accepted Answer

To specify the conditions a user story must meet to be accepted as complete

Answer

Acceptance criteria define the specific conditions that a user story must satisfy for it to be considered done and accepted by the product owner.

Question 2

Which format is most commonly used to write acceptance criteria in Agile?

Accepted Answer

Given-When-Then (Gherkin syntax)

Answer

The Given-When-Then format (Gherkin syntax) is widely used for acceptance criteria because it clearly defines context, action, and expected outcome in plain language.

Question 3

Who is primarily responsible for defining acceptance criteria for user stories?

Accepted Answer

The product owner in collaboration with stakeholders

Answer

Acceptance criteria are primarily defined by the product owner in collaboration with stakeholders and the development team to ensure shared understanding of requirements.

Question 4

When should acceptance criteria be written for a user story?

Accepted Answer

Before the sprint begins, ideally during backlog refinement

Answer

Acceptance criteria should be written before development begins, typically during backlog refinement, to provide clear guidance to the development team before they start work.

Question 5

Which of the following is a characteristic of well-written acceptance criteria?

Accepted Answer

They are testable, specific, and focused on user outcomes

Answer

Well-written acceptance criteria are testable, specific, and focused on what the user needs to accomplish, not on how the system implements the solution.

Agile Business Analysis Practice Test

Agile Business Analysis Practice Test

Agile Business Analysis Acceptance Criteria and Definition of Done