What Done means before work counts as finished
Definition of Done is the team's agreement that an increment is actually finished. The acceptance criteria are met. The work is integrated and tested to the level the team agreed. Known defects are not left inside the increment and then called complete.
Done is a property of the increment, shared by the team, not a status one person sets because the coding is over. When a sprint full of bug fixes is counted the same as a sprint that shipped the commitment, the delivery number stops meaning what the team thinks it means.
Defects found after the team called the work Done are escaped defects. They belong in the quality picture, separate from the count of work that met the commitment.
How a team uses Done
During the sprint. Completed means Done. Work that still has open defects, or that was added after the commitment, is part of the sprint story, and it is not the same number as work that met Done.
Sprint review. Show the increment that passed that bar. If the team cannot point to the checks that were met, the item is not finished yet, even when the status says otherwise.
Where this shows up in Sprint Vitals
Done is a delivery and quality question. Delivery keeps the commitment, what was added or removed, what completed, and what spilled. Quality stays beside that count: defects created, defects closed, and escaped bugs, so a sprint spent fixing defects does not look like a sprint that shipped the commitment.
A Jira admin approves Marketplace apps for the site. If you are the scrum master, send them the install link. If you already have Sprint Vitals, the manual explains how to read those numbers on the board.
Checklist download
A one-page definition of done checklist is coming. You will be able to leave an email on this page and receive it. Until then, the checks above are the working list.
Done decides what counts as finished. Definition of Ready decides what enters the sprint.