Quiz – Acceptance Criteria

Question 1 of 6

1. Question

What are acceptance criteria?

Testable conditions defining when a user story is truly done

Correct Incorrect Correct answer

Optional notes developers may ignore

Correct Incorrect Correct answer

A vague summary of the project vision

Correct Incorrect Correct answer

The team’s estimate in story points

Correct Incorrect Correct answer

Question 2 of 6

2. Question

In Scrum, acceptance criteria are essential to which practice?

The Definition of Done

Correct Incorrect Correct answer

The sprint retrospective agenda

Correct Incorrect Correct answer

The velocity chart

Correct Incorrect Correct answer

The stakeholder budget

Correct Incorrect Correct answer

Question 3 of 6

3. Question

A good acceptance criterion should be:

Testable, specific, and measurable

Correct Incorrect Correct answer

Broad, open-ended, and flexible

Correct Incorrect Correct answer

Written only after release

Correct Incorrect Correct answer

Known only to the product owner

Correct Incorrect Correct answer

Question 4 of 6

4. Question

What happens when a team writes clear acceptance criteria?

Sprints run smoother and velocity increases

Correct Incorrect Correct answer

Developers build without knowing the goal

Correct Incorrect Correct answer

Testing becomes impossible

Correct Incorrect Correct answer

Stakeholders lose all visibility

Correct Incorrect Correct answer

Question 5 of 6

5. Question

Match each role to what acceptance criteria give them.

Sort elements

Know exactly what to build
Know precisely what to verify
Confidence value is delivered

Developers

Correct Incorrect Correct answer

Testers

Correct Incorrect Correct answer

Product owner

Correct Incorrect Correct answer

Question 6 of 6

6. Question

Fill in the blanks.

Acceptance criteria must be Fill in the blank 1 of 3 and Fill in the blank 2 of 3 , and they form part of the Definition of Fill in the blank 3 of 3 .