Practise the standard verbs for keeping a shared definition of done meaningful.
0 / 5 completed
1 / 5
Fill in: 'We ___ a shared definition of done before sprint one even starts, so 'done' means the same thing to every engineer, not a different thing to each person on the team.'
We 'agree a definition' — the standard, simple collocation for reaching team consensus on completion criteria. The other options are less idiomatic here.
2 / 5
Fill in: 'Leaving 'done' undefined and up to individual interpretation can ___ a ticket closed as complete that still has no tests and no documentation attached.'
We say an undefined standard will 'leave' incomplete work closed as done — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every completed ticket against the definition of done explicitly, rather than trusting a status change alone to mean the checklist was actually followed.'
We 'check a ticket' — the standard, simple collocation for verifying work against agreed completion criteria. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ the definition of done periodically as the team's practices mature, since a checklist written a year ago rarely still matches how the team actually works today.'
We 'revise a definition' — the standard, simple collocation for updating agreed criteria over time. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a ticket back to in-progress the moment it fails the definition of done, rather than quietly letting an exception slide just this once.'
We 'move a ticket' — the standard, simple collocation for changing a ticket's status to reflect its real state. The other options are less idiomatic here.