Which of the following describes what user story acceptance criteria are?

Acceptance criteria are a set of predefined conditions that a user story must satisfy to be accepted as "done" by the product owner and stakeholders. They clarify the story's requirements and scope, remove ambiguity, and provide a clear basis for testing. By defining the pass/fail conditions for the intended functionality, they ensure that the developed feature meets the business objective before it is considered complete.

A. This describes the standard format of a user story ("As a , I want , so that "), not its acceptance criteria.

C. While they can be formatted as a checklist, their fundamental purpose is to define the "done" state, not just list activities to be performed.

D. This describes the "so that..." clause of a user story, which articulates the business value or rationale, not the specific conditions for completion.

1. Guidewire. (2021). SurePath for Agile Projects Delivery Guide. Section 4.2: "Product Backlog Management". This guide explains that acceptance criteria are "the conditions of satisfaction" that determine when a story is complete.

2. Guidewire Education. (2022). A15 - Guidewire's Agile Project Delivery. Module: "User Stories". The course material defines acceptance criteria as the testable conditions that must be met for a story to be marked as done.