The 'definition of done' is a great way to reach [[20250728012913-alignment]] on when projects are actually complete.
You can have different definitions, checklists, etc. as long as the team is agreed on it. Typically the lead of the project defines the definition of done, as it's important to be comprehensive and correct. Ensure that it's collaborative, so it doesn't neglect any disciplines.
Although similar to acceptance criteria, a definition of done is applied generically to everything you are trying to ship. Acceptance criteria differs and is unique to the user story or feature in question.
I think having a strict definition of done is especially important for juniors and to help onboard members to your team, as everyone has slightly different definitions.