Pick a preset. Tick the items that fit your team. Copy a markdown checklist your team will actually use.
Tap to toggle. Tap × to remove. Add custom items below.
0 items · tip: shorter is better. A 6-item DoD that everyone uses beats a 14-item one that nobody reads.
Loading…
SprintFlint lets you pin a Definition of Done to every issue and tick items as work progresses. No more wiki-poster DoD that nobody reads.
Start FreeShort. Aim for 5-8 items for a small team, 10-12 for a regulated or enterprise team. Anything longer becomes wallpaper — nobody reads a 20-item checklist on every ticket.
No. The DoD reflects the work and the standards of the team doing it. Backend, frontend, mobile, and design teams all have different "done" criteria. Share a foundation; let teams tailor the rest.
Acceptance criteria are per-ticket — what specifically counts as "this story works." DoD is the team-wide bar that applies to every ticket on top of that. Both matter; they answer different questions.
Make it visible at PR-review time and at ticket-close time. Best version: a checkbox list pinned to the issue itself. The reviewer or PM ticks the boxes before "done."
"Logging or metrics added for observability." Most bugs in production are debugged via logs and metrics. If your DoD doesn't include this, you'll find out the hard way.
By the team, in a 30-minute discussion. The manager facilitates and asks questions ("what would catch the bugs we shipped last quarter?"). Owned-by-team DoD gets used. Imposed-from-above DoD gets ignored.
Once per quarter, or after any incident where a "done" ticket caused a problem in production. The DoD is a living document — if it stops catching bugs, evolve it.
SprintFlint shows your Definition of Done on every ticket and tracks completion automatically. Free for the first 300 tickets — no card.