Definition of Ready (user story) checklist template
For product owners and teams refining a story before sprint planning. The story must state who needs it, what and why, have testable acceptance criteria, known dependencies and a team estimate, and fit one sprint or be split.
- App: Checklist Flow for Jira
- Category: Software delivery
- Edition: Installs with or without a paid licence
- Items: 10 items, 4 required
- Suggested for: Story, Epic
Items
#Clear
| Item | Required |
|---|---|
| The story states who needs it, what they need and why | Required |
| Acceptance criteria are written and testable | Required |
| Out of scope items are listed | Optional |
| UX designs or mockups are attached when the change has a user interface | Optional |
Feasible
| Item | Required |
|---|---|
| Dependencies on other teams or systems are known | Required |
| The team has estimated the story | Required |
| The story fits in one sprint, or it has been split | Optional |
| Test approach is agreed | Optional |
Approved
| Item | Required |
|---|---|
| Product owner has prioritised the story | Optional |
| Open questions are answered or have an owner | Optional |
Use it
#In a Jira work item, open the Checklist Flow panel, then Template library in the Templates section. Find the template under its category, use Preview to see the items and Install to add it to your site's templates. From then on you can apply it to any work item, or, with a paid licence, have it added automatically by issue type.
Related
#- Checklist Flow for Jira documentation
- Jira checklist templates: all 49 templates