CAPM Practice: Determine how to gather requirements

Acceptance criteria define what 'done' looks like for a user story — the specific, testable conditions that must be true for the story to be accepted. They bridge requirements and testing, preventing subjective disputes about completion.

**Why not A:** Acceptance criteria in agile do not refer to criteria for accepting or onboarding team members. Acceptance criteria define the specific conditions that a user story or feature must satisfy to be considered complete and ready for the product owner to accept the work as done.

**Why not B:** Acceptance criteria are not related to project charter approval. Charter approval involves organizational governance and project authorization, which is a separate concern. Acceptance criteria operate at the user story level, specifying testable conditions for feature completeness.

**Why not D:** Acceptance criteria do not define documentation quality standards. While documentation may be part of a definition of done, acceptance criteria specifically describe the functional and non-functional conditions under which a particular user story is considered successfully implemented and verified.