Theme, epic, story, task and work package
Five words for work at different sizes, and one for when and by whom it is delivered.
In short
Work is split by size into a tree: a theme holds epics for quarters or years, an epic is a capability over weeks or months, a story is a slice with code done in days, and a task is a slice without code. A work package is not in the tree: it is the delivery container — owner, dates, budget — that the work is planned in.
Side by side
| Size | Contains | Example | |
|---|---|---|---|
| Theme | Quarters–years | Epics | Self-service for patients |
| Epic | Weeks–months | Stories, tasks, defects | Online rescheduling |
| Story | Days, with code | Subtasks | Move an appointment from the e-mail link |
| Task | Hours–days, no code | Subtasks | Grant calendar access to the booking service |
| Work package | A delivery | Planned epics, stories, tasks | Release 1 — spring launch |
How to tell them apart
- Does it change code? Story. Does it not? Task.
- Can it be finished in days? If not, it is an epic that needs splitting.
- Is it about when, by whom and on what budget rather than what? Work package.
- Is it a direction rather than a deliverable? Theme.
Example: Clinic Booking
Theme "Self-service for patients" → Epic "Online rescheduling" → Story "Move from the e-mail link" and Task "Grant calendar access", all planned in Work package "Release 1 — spring launch".
Why the difference matters to an agent
The story is where an agent works; the levels above it give it context. An agent that can see its epic avoids duplicating a neighbouring story, and a work package tells it what belongs to the current delivery.