Acceptance criteria

Roles that need it

• Product Owner
• Product Owner (Banking)
• Business Analyst
• Business Analyst (Banking)
• Project Manager

Skills it belongs to

• Requirements gathering and documentation
• User acceptance testing coordination

Related concepts

• User storyA user story is a short requirement written from the user's point of view, usually in the form "As a [role], I want [capability] so that [benefit]". It is small enough to deliver in one sprint and comes with acceptance criteria.
• User acceptance testing (UAT)User acceptance testing is the final test phase in which business users check that a new or changed system supports their real processes and meets the agreed requirements and acceptance criteria. Formal UAT sign-off is usually a condition for go-live.
• RequirementsRequirements are documented statements of what a solution must do or achieve. Business requirements describe the need, functional requirements describe system behaviour, and non-functional requirements set qualities such as performance or security. Each should be clear, testable and traceable.

Sources

• ISTQB Glossary, International Software Testing Qualifications Board (external site) accessed 31 Oct 2026
• The Scrum Guide, Schwaber and Sutherland (external site) accessed 31 Oct 2026

Updated 31 Oct 2026.