Acceptance Criteria
Updated · Tech checked
Testable statements that define when a deliverable is done, agreed with the customer before build starts.
Good acceptance criteria are specific, binary and customer-confirmed: "Given a duplicate invoice ID, the pipeline quarantines it and alerts - it never double-posts." They anchor testing, demos and sign-off, and they defuse scope disputes because 'done' was written down in advance.