Acceptance criteria that survive handoff
How Requirements Analysis Lab participants turn fuzzy tickets into statements QA and engineering can share.
A ticket that says “make checkout better” is not a requirement. It is a wish. In class we force the wish through three filters: observable outcome, boundary conditions, and evidence of done.
Observable outcomes name what a user or system can verify. Boundary conditions list the messy edges—currency, guest users, partial failures. Evidence of done points to a test, a log, or a screen state.
We also practice saying no. If a stakeholder will not supply an edge case, the criterion is marked incomplete and the story stays out of the sprint.
The goal is not prettier Jira. The goal is fewer surprises when the build reaches QA.