Definition of Ready & Done template
The checklists a story must pass before the team takes it, and before anyone calls it done.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- Definition of Ready
- ☐ Written as a user story with a clear why · ☐ Acceptance criteria agreed · ☐ Designs attached (if UI) · ☐ Dependencies identified · ☐ Estimated, ≤ 8 points
- Definition of Done
- ☐ Code reviewed and merged · ☐ Tests written and passing in CI · ☐ Acceptance criteria verified by PO · ☐ Docs / release notes updated · ☐ Deployed to production behind a flag
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Add notes fast. Press S for a sticky note in the middle of your view. A sticky is a box like any other: link it, recolour it, resize it.
- Move cards between columns. Drag a sticky into another column; select several with a drag box to move them together.
- Present it. Frames become slides when you present, and the laser pointer helps you walk people through the board.
Good for
- definition of done
- definition of ready
- scrum
- quality
- product owner
- Running a retrospective or planning session
- Making the state of work visible on one board
- Agreeing on what “ready” and “done” mean
Related templates
Product backlog
A ranked backlog with type, estimate and readiness, plus backlog health and the next refinement session.
Sprint review
Run the sprint review: a timed agenda, planned vs done, what was demoed, stakeholder feedback and backlog changes.
Sprint planning
Sprint goal, team capacity, the stories pulled in, and the risks — everything a sprint planning meeting needs.
Sprint retrospective
What went well, what could be better, and action items with an owner — the standard Scrum retro.
Model evaluation plan
Metrics, datasets, targets and owners for evaluating an LLM or ML model, plus the gate a release must pass.
Code review checklist
What to look for in a pull request, from correctness to security, so reviews are fast and consistent.