Stage 3 · Lesson 2 of 8
Tickets and acceptance criteria
Work usually arrives as a , a short written task in a tool such as Jira, Linear or Issues. A good ticket says what problem it solves and for whom. It also lists the acceptance criteria: the checks that must be true for the work to count as done.
For example, "the user sees an error message if the email is invalid." Before you start, read the whole ticket and restate it in your own words. Ask about anything vague, such as (unusual inputs or situations), error messages or which screens are affected.
Update the ticket as you learn things, and link your to it. Clear tickets make estimates possible, which is the next topic.
Common trapstarting to code from the title alone, then learning in review, or from a , that the expected behaviour was different.
A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it
Resources for this stage
Start with· follow one of these
- GuideFreeAtlassian Agile Coach
Atlassian · Beginner
Short, practical pages on standups, estimation, sprints and retros, whatever tool your team uses
- GuideFreeThe Scrum Guide (2020)
Ken Schwaber and Jeff Sutherland · Beginner
The original definition of sprint events in half an hour, so the vocabulary makes sense
Practise
Keep handy
Also worth your time
- Shape UpGo deeper
A different way to plan work than sprints, useful for understanding why teams choose their process