Acceptance criteria

• Preparing sprint-ready stories for engineering.
• Reducing QA ambiguity and release risk.
• Aligning product and design intent before build.

Clear acceptance criteria improve delivery predictability and reduce defects caused by interpretation gaps.

Write criteria as observable behavior with edge cases and constraints. Keep each criterion independently testable and tied to user value.

Given a logged-in user, when they leave onboarding at step 3, then progress is saved and restored at next login.

• Using vague wording like fast, intuitive, or robust.
• Mixing multiple outcomes in one criterion.
• Skipping negative and edge-case scenarios.