TEMPLATESJIRA · TSK
Task
A discrete piece of work described so any team member can continue it without further clarification.
Paste the blank into the ticket description and overwrite the [brackets].
Prompt and blankWorked example
01Summary
Verb, deliverable, context. Someone scanning the board should know what you'll produce.
[Action verb] + [deliverable] + [context]
Example
Draft data migration approach document for the PPM tool
02Description
Write it so anyone on the team could pick the task up cold. Don't leave anything in your head. Say what done looks like in the Expected Output line.
- **Objective:** [purpose of the task] - **Background / context:** [why we're doing this; link the business case, decision or related ticket] - **Scope:** [included / excluded] - **Instructions / steps:** [concrete steps or guidance, if applicable] - **Expected output / deliverable:** [the document, configuration or evidence that shows it's done]
Example
- Objective: Agree how project data moves from spreadsheets into the new PPM tool.
- Background / context: Cutover is planned for March (see DEC-14). The migration approach is the last open item before vendor onboarding.
- Scope: Included: active projects, budgets, risks. Excluded: closed projects older than 2 years.
- Instructions / steps: 1. Inventory the sources with the PMO. 2. Map fields to the PPM schema. 3. Define cleansing rules. 4. Propose cutover and rollback steps.
- Expected output / deliverable: A five-page approach document in Confluence, reviewed by the PMO lead and Data Protection.
03Definition of Done
Three or four criteria that a reviewer can check: the outcome, how clear it is, and whether the next person can pick it up. Use your team's standard if you have one.
- [ ] [Measurable outcome] - [ ] [Clarity of result] - [ ] [Handover readiness]
Example
- Approach document published and linked to the ticket.
- Reviewed by the PMO lead and Data Protection, with comments resolved.
- Open decisions raised as separate tickets and assigned.