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

To define the technical architecture of the solution

Answer

To document the project timeline and milestones

Answer

To identify the stakeholders responsible for testing

Question 2

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

Accepted Answer

Given-When-Then (Gherkin syntax)

Answer

Use case narratives

Answer

State transition diagrams

Answer

Entity-relationship diagrams

Question 3

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

Accepted Answer

The product owner in collaboration with stakeholders

Answer

The development team

Answer

The Scrum Master

Answer

The project manager

Question 4

When should acceptance criteria be written for a user story?

Accepted Answer

Before the sprint begins, ideally during backlog refinement

Answer

After the user story has been developed

Answer

During sprint review

Answer

After the product is released to production

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

They are written in technical implementation terms

Answer

They describe how the feature should be technically built

Answer

They list all edge cases exhaustively before any are tested

Question 6

What is the relationship between acceptance criteria and the Definition of Done in Agile?

Accepted Answer

Acceptance criteria are story-specific while the Definition of Done applies to all stories team-wide

Answer

They are identical and can be used interchangeably

Answer

The Definition of Done replaces acceptance criteria for all stories

Answer

The Definition of Done is only relevant for sprints, not individual stories

Question 7

A business analyst notices that a user story entering sprint planning has no acceptance criteria. What is the BEST course of action?

Accepted Answer

Postpone the story until acceptance criteria are added during backlog refinement

Answer

Proceed with development based on the story description alone

Answer

Have the development team create acceptance criteria during the sprint

Answer

Remove the story from the backlog permanently