The team’s completion checklist
Finishing the code may still leave reviews, tests, or documentation unfinished. A team might require approved code review, passing tests, accessibility checks, and updated user documentation. Its definition of done records these checks so the team applies them consistently.
Done is different from accepted
Acceptance criteria state what one work item must do. The definition of done covers quality checks expected across the team’s work.
A useful checklist is thorough enough to catch unfinished work and practical enough to follow. Teams update it as their needs and risks change.