CAPM Practice: Validate requirements through product delivery

The DoD ensures that 'done' means the story not only works technically but meets acceptance criteria (requirements validation), passes review, and is deployable. This prevents incomplete validation — stories that pass technical tests but don't meet business requirements from being marked done.

**Why not A:** The definition of done is not a project-level completion criterion controlled solely by the project manager. It is a team-level agreement that applies to individual work items such as user stories or features. Project completion is governed by broader acceptance criteria, project scope, and formal sign-off processes.

**Why not B:** The DoD is not limited to technical code quality standards owned by developers alone. It is a cross-functional checklist that may include testing, documentation, stakeholder review, and deployment readiness. All team members, including BAs and testers, contribute to and use the DoD.

**Why not D:** The DoD is not a formal customer acceptance document. It is an internal team agreement used throughout delivery to ensure consistent quality for each increment. Formal customer acceptance is a separate process that typically occurs at milestone deliveries or project completion.