Backlogs are organized in levels, from big to small. Tools name them differently; the idea is the same:
- Epic: a large body of work, often a quarter or more. "Online returns."
- Feature (in some tools): a capability inside an epic, delivered over a few sprints. "Return labels."
- Story: a small, valuable slice that fits in a sprint. "Download a return label as a PDF."
- Task: a piece of technical work inside one story, owned by the team. "Add the label endpoint." Tasks are not shown to stakeholders as value.
Acceptance criteria belong on stories. Epics carry the goal and how success is measured; tasks carry no business value on their own, which is why "create the table" is a task, never a story.
Keeping the levels straight makes the backlog readable: a sponsor reads epics, a product owner orders stories, developers plan tasks.