In Agile development, what is the "Definition of Done" and why is it critical?

Correct answer: A shared agreement on what criteria must be met before a user story is considered complete

Option B is correct because the Definition of Done is a shared, explicit list of criteria that every increment must satisfy before the team considers a user story complete, ensuring a consistent and transparent quality standard across the team. Option A is incorrect because the final deployment of all project deliverables describes project closure or a release, not the per-story acceptance criteria that the Definition of Done establishes. Option C is incorrect because individual task completion tracking is a personal or task-board activity; the Definition of Done is a collective agreement about quality, not a tool for tracking individual output. Option D is incorrect because the project completion report is a closing document summarizing outcomes, not a quality gate applied to each user story during development.