CAE Definition of Done & Acceptance Criteria 2

Question 1

How should Acceptance Criteria be written to be most effective in Agile?

Accepted Answer

As clear, testable conditions that define when a story is complete

Answer

As vague goals that allow creative interpretation by the team

Answer

As technical specifications written exclusively by developers

Answer

As business KPIs linked to organizational strategy

Question 2

The Given-When-Then (GWT) format for writing Acceptance Criteria is associated with which practice?

Accepted Answer

Behavior-Driven Development (BDD)

Answer

Test-Driven Development (TDD)

Answer

Continuous Integration (CI)

Answer

Domain-Driven Design (DDD)

Question 3

What does it mean for the Definition of Done to evolve over time?

Accepted Answer

The DoD may become more stringent as the team improves its practices

Answer

The DoD should be simplified as the team matures to speed up delivery

Answer

The DoD should be replaced entirely by Acceptance Criteria over time

Answer

The DoD should be fixed at the project start and never changed

Question 4

What is the primary risk of having an unclear or weak Definition of Done?

Accepted Answer

Technical debt may accumulate as incomplete work is incorrectly considered done

Answer

The team may deliver too many features too quickly

Answer

The Product Owner may add too many items to the backlog

Answer

Stakeholders will request more frequent Sprint Reviews

Question 5

In Agile, what is meant by 'undone work'?

Accepted Answer

Work that was marked complete but does not fully meet the Definition of Done

Answer

Work that was never started during a Sprint

Answer

Work that is currently in progress but not yet completed

Answer

Work items that were removed from the Product Backlog

Question 6

Which Agile Manifesto principle best supports the use of Acceptance Criteria to measure progress?

Accepted Answer

Working software is the primary measure of progress

Answer

Responding to change over following a plan

Answer

Welcome changing requirements, even late in development

Answer

Our highest priority is to satisfy the customer through early and continuous delivery

Question 7

When should Acceptance Criteria be defined for a user story?

Accepted Answer

Before or during Sprint Planning so the team understands scope before committing

Answer

After the Sprint begins so the team has initial implementation context

Answer

During Sprint execution as the team discovers requirements organically

Answer

At the Sprint Review so stakeholders can approve them retrospectively