Guides · Definition of done
What is a definition of done
GAO's guide says that, before development, an overall definition of done and acceptance criteria are established, and that the definition of done encapsulates both the acceptance criteria and additional activities such as testing or compliance checks — so the developers and the product owner share an understanding of what "complete" means. If "done" was not agreed before development, the demo has no shared test. This is a short companion to Verifiable requirements and a definition of done, not a second copy of it.
the GAO Agile Assessment Guide is cited here as the September 2020 Exposure Draft, not as a later final edition.
The GAO Agile Assessment Guide. On the complete / feasible / verifiable practice, already quoted in batch 1: "Prior to development, an overall definition of done and acceptance criteria for requirements are established." "A definition of ready may also be established as Agile teams work to set an expectation of the level of detail needed before teams can start development on a user story."
In the test-and-validate section: "Then, as part of the backlog refinement process, the team establishes the definition of done and defines acceptance criteria for each user story, so that the developers and product owner have a shared understanding of what it means for a piece of work to be considered complete. The definition of done encapsulates both the completion of acceptance criteria and the completion of additional activities, such as testing or compliance checks. User story acceptance criteria is specific to just one user story and documents the product owner requirements that must be met, whereas the definition of done applies to all user stories." "In order to validate that requirements have been met, the product owner should identify acceptance criteria for every user story prior to development of the story (often as part of backlog refinement or planning for an iteration) and the program should agree on a definition of done (e.g., must meet acceptance criteria and be 508 compliant)." The "508 compliant" example is GAO's, in a federal-auditor guide; it is not treated as an OSGA house requirement. "The acceptance criteria and definition of done constitute the expectations for the user story against which the requirement will be validated and either accepted or rejected by the product owner." The checklist: "The product owner agrees to and accepts the definition of done for each user story."
GAO's distinction
Overall definition of done and acceptance criteria prior to development. Definition of done equals acceptance criteria plus additional activities such as testing or compliance checks. Acceptance criteria are specific to one user story and document the product owner's requirements. The product owner agrees to and accepts the definition of done for each story. Definition of ready, if used, is about the detail needed to start. This page does not invent a numeric house checklist.
Test and validate the system as it is being built is the build-time sibling. Work prioritized for customer value is the ordering sibling, where value is reevaluated as needs change.
The first conversation still ends with a yes, a no, or a better idea, at Start. The dashboard remains "opening soon."
The useful next step is to agree the definition of done, and the acceptance criteria, before the next story starts. If something on this page is wrong, write to us.