How to work with tickets and acceptance criteria as a junior developer
How to read a ticket, find what it doesn't say, ask good questions, and turn acceptance criteria into tests, with examples from realistic product tickets.
Most work on a software team arrives as a ticket: a short message describing what's needed, often written quickly by a product manager or a colleague. Reading tickets well is a core junior skill, and almost nobody teaches it.
Anatomy of a ticket
A typical ticket has:
- A title ("Shipped orders getting cancelled").
- Context: who's affected and why it matters.
- The request, often informal and incomplete.
- Acceptance criteria: the precise conditions for "done".
Here's a realistic example from a parking-fee project:
The tariff: stays of 15 minutes or less are free. Otherwise €2.50 per started hour. Never more than €15.00 for one stay. €6.00 if the car came in at 18:00 or later and leaves by 08:00 the next morning, if that's cheaper.
Read it three times
- First read: the goal. What problem does this solve for whom?
- Second read: the rules. List every rule as a bullet. "Started hour" means 61 minutes is two hours. "By 08:00" includes 08:00.
- Third read: the gaps. What isn't said? What if the car stays exactly 15 minutes? What about a stay that crosses midnight? What about 24:00?
Write the gaps down. Some you can decide sensibly and note in your design; others need a question.
Asking good questions
Good questions are specific and come with a proposal:
- Weak: "How should midnight work?"
- Strong: "For stays across midnight I'll compute the length as (exit − entry + 1440) mod 1440, so 23:30 → 00:10 is 40 minutes. OK?"
From acceptance criteria to tests
Each criterion becomes one or more tests, and each boundary becomes a pair of tests on either side:
- "15 minutes or less is free" → tests for 15 minutes (free) and 16 minutes (€2.50).
- "Per started hour" → tests for 60 and 61 minutes.
- "In at 18:00 or later" → tests for 17:59 and 18:00.
If you can't write a test for a criterion, it isn't precise enough yet: ask. More on tests in unit testing in C++.
Practise on realistic tickets
Every Devventura project starts with tickets written this way, slightly ambiguous on purpose, with acceptance criteria and tests. Good ones to practise on:
- Parking fees for ParkPoint: boundaries everywhere.
- Stock counts for Pantry & Co.: rules that must never break.
- The task list behind Tasklane: dates, IDs and ordering rules.
Next, turn your notes into a plan: design docs for junior developers.
Questions and answers
- What are acceptance criteria?
- A short list of conditions a piece of work must meet to count as done, written precisely enough to test. They turn 'it should handle bad input' into 'a quantity of zero or less is refused and nothing changes'.
- Is it OK to ask questions about a ticket?
- Yes. Asking early is expected and saves everyone time. Bring specific questions with a proposed answer, like 'I'll treat 08:00 as still inside the evening rate unless you say otherwise.'
Practise it in a project
These projects put this guide to work, with tickets, tests and code review.
ParkPoint
Parking fees for ParkPoint
Compute what ParkPoint's pay machines charge: stays across midnight, a free grace period, a daily cap and an evening flat rate.
- time arithmetic
- integer rounding
- business rules
- boundary testing
Pantry & Co.
Stock counts for Pantry & Co.
Track stock as goods arrive and leave Pantry's warehouse, and tell the buyers what to reorder.
- classes
- invariants
- std::map
- input validation
Tasklane
The task list behind Tasklane
Build the core of Tasklane's to-do list: strict due dates, stable task IDs and an agenda in the right order.
- date validation
- enums
- stable IDs
- multi-key sorting
Read next
- How to write a design doc: a short guide for junior developers
What a design document is for, a half-page template (components, data structures, trade-offs, open questions) and a worked example, before you write any code.
- Code review checklist for junior developers
What senior engineers look for in a code review, as a practical checklist: correctness, edge cases, tests, naming, structure and performance, with C++-specific points.