Examples:
• Healthcare – Patient Portal Login Feature: “A new login function for patients must accept Patient Identification numbers, support password reset, and load within 2 seconds on mobile and desktop apps.”
• Retail – Self-Checkout Receipt Printing: “The self-checkout machine must print a receipt within 5 seconds of payment, include store branding, and show itemised purchases with totals.”
• IT – Email Notifications for Password Changes: “After a user changes their password, they must receive a confirmation email within 1 minute, with the correct username, timestamp, and a link to support.”

When to use:
Use when defining a user story, typically during backlog refinement or sprint planning, to ensure development teams understand the specific requirements for successful completion.

What It Might Look Like in Practice:
• Acceptance criteria listed underneath each user story in a system like Jira or Azure DevOps.
• Typically formatted as bullet points or in “Given/When/Then” format.
• Used by testers to write test cases and verify story completion.