Which criteria are necessary for determining if a story is marked as "Done"?

A story is marked as "Done" primarily when all acceptance criteria are met. Acceptance criteria define the specific conditions under which a piece of work will be considered complete from the perspective of the stakeholders. They provide a clear understanding of what needs to be achieved for the story to fulfill its purpose and ensure that it meets the expectations set out during the planning phase.

Meeting the acceptance criteria is vital because it assures that the functionality behaves as intended and satisfies user requirements. This aspect is essential in Agile methodologies, where feedback and collaboration shape the development process.

Other criteria, while important for the overall quality and documentation of the project, do not exclusively determine if a story is considered “Done.” For instance, the completion of the high-level design, passing unit tests, or updating documentation are all significant activities that support the project’s progress and quality assurance, but they do not encompass the core definition of completion for a user story. Focusing on acceptance criteria aligns with Agile principles, ensuring that the end product meets user needs effectively.