Guides · Verifiable requirements
Verifiable requirements and a definition of done
GAO's Agile Assessment Guide treats backlog items and user stories as forms of requirements, and it asks that requirements be complete, feasible, and verifiable, with a definition of done and acceptance criteria established before development. If acceptance criteria did not exist before development, the demo has nothing official to pass against.
This is a field note about being able to check the work, not a stage-gate product pitch, and not a rewrite of Each wave ends with a check. That essay is the house sibling. The document is the September 2020 Exposure Draft of the GAO Agile Assessment Guide, the same draft used in the working-software and MVP guides. It is not called a later final edition. This page does not invent a numeric "definition of done" checklist that is not in the opened text, and it does not use CHAOS rates.
The GAO Agile Assessment Guide says "This guide considers both product backlog items and user stories to be a form of requirements."
Among the chapter's named practices: "Ensure requirements are complete, feasible, and verifiable." "Test and validate the system as it is being developed." "Ensure work is contributing to the completion of requirements."
On the complete / feasible / verifiable practice: "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."
Stories still count as requirements
GAO is explicit: backlog items and user stories are a form of requirements. Informality of format is not an excuse for unverifiable work. Complete, feasible, and verifiable is the test. A definition of done and acceptance criteria come prior to development. A definition of ready, if used, is about the detail needed to start. Testing happens as the system is being developed, not only at the end.
The heading "Test and validate the system as it is being developed" is opened. The detailed body of that subsection was not quoted in the brief, and it is not reconstructed here. A later companion can go deeper once that subsection is opened in full.
This page does not invent a house gate, a client review, or a pass rate.
The first conversation still ends with a yes, a no, or a better idea, at Start.
The useful next step is to write the acceptance criteria before the next increment starts. If something on this page is wrong, write to us.