Explicit statements of what users expect a feature to do, written before or during build so there's an unambiguous bar for 'done.' Acceptance criteria translate a User Personas / Roles need into testable expectations, and they are what QA and Defect Tracking checks against — a feature that fails its acceptance criteria in QA becomes a defect, not a completed item.
Из тем: The Product Operating Model