Themes, epics, stories, tasks and work packages
Two axes: a value tree for what you build, and work packages for when and by whom.
For: Project lead, Product owner
Value tree
Theme → Epic → Story or Task → Subtask. One parent each, one level up. Stories and tasks are peers under an epic; both can have subtasks.
Work packages
Delivery containers: epics, stories and tasks are planned in one package; packages carry owner, dates and budget and can nest.
Linking to requirements
- Implements: the requirement the work brings to life.
- Covers: the acceptance criteria a story or task must satisfy.
- Serves: the objective a theme or epic contributes to.