Agile guide · Agile practices
Epics vs Stories vs Tasks: Agile Work Hierarchy Explained
Epics, user stories and tasks are three levels of the Agile work hierarchy. An epic is a large goal spanning several sprints, a user story is a small slice of user value that fits in one sprint, and a task is a technical step needed to complete a story.
Key takeaways
- Epics are large goals, stories are small slices of user value and tasks are technical steps.
- Stories and epics deliver value; tasks do not on their own.
- The product owner shapes epics and stories; developers create tasks.
- Keep the hierarchy simple and consistent across the team.
The hierarchy at a glance
| Level | What it is | Typical size | Usually written by |
|---|---|---|---|
| Initiative or theme | A broad objective or area of focus | Months to a year or more | Leadership, product management |
| Epic | A large body of work with one goal | Several sprints | Product owner or product manager |
| User story | A small slice of value for a user | A few days; fits in one sprint | Product owner, with the team |
| Task | A technical step to complete a story | Hours to a day | The developers doing the work |
Key differences
| Epic | User story | Task | |
|---|---|---|---|
| Purpose | Group related stories under a goal | Deliver value a user can see | Break a story into steps |
| Viewpoint | Business or user outcome | User | Technical or team |
| Delivers value on its own? | Yes, once its stories are done | Yes | No |
| Estimated in | Rough size or sum of story points | Story points or similar | Hours, or not estimated |
| Appears on | Roadmap and release plan | Product and sprint backlogs | Sprint backlog and task board |
| Completed when | Its goal is met | Acceptance criteria and Definition of Done are met | The step is done |
Worked example
Epic: Online class booking for a gym chain.
- Story: As a member, I want to book a place in a class so that it is reserved for me (5 points).
- Task: build the booking button and confirmation screen (4 hours).
- Task: add the booking endpoint and capacity check (6 hours).
- Task: write automated tests for full and available classes (3 hours).
- Task: update the timetable to show remaining places (2 hours).
- Story: As a member, I want to cancel a booking so that someone else can take my place (3 points).
- Task: add a Cancel button with confirmation (2 hours). Task: release the place and notify the waiting list (5 hours).
The product owner tracks the epic on the roadmap, the team plans stories in sprint planning, and developers create and update tasks during the sprint.
How to break work down
- Start from an outcome on the roadmap and write it as an epic with a success measure.
- Split the epic into user stories using patterns such as workflow steps, user types or happy path first.
- Refine the top stories until they meet INVEST and can be estimated; see backlog refinement.
- In sprint planning, the developers break the selected stories into tasks.
- Track tasks daily on the task board; close the story when all criteria are met.
- Close the epic when its goal is achieved, even if some lower-value stories remain unbuilt.
Common mistakes
- Using tasks to represent user value, so the backlog becomes a to-do list with no clear outcomes.
- Creating epics so big they never close.
- Estimating tasks in hours and stories in points, then adding them together.
- Assigning tasks to people at sprint planning rather than letting the team pull work.
- Adding extra levels (sub-epics, sub-sub-tasks) that make the backlog harder to read.
Free templates for this topic
Frequently asked questions
Epics vs stories vs tasks: what is the difference between an epic and a story?
An epic is a large goal that takes several sprints; a story is a small, user-focused slice of that goal that fits in one sprint.
Epics vs stories vs tasks: what is the difference between a story and a task?
A story delivers value to a user; a task is a technical step that helps complete a story and has no user value on its own.
Epics vs stories vs tasks: do tasks need story points?
Usually not. Story points are applied to stories; tasks are often estimated in hours or not estimated at all.
Epics vs stories vs tasks: who creates tasks?
The developers who will do the work, typically during sprint planning and throughout the sprint.
Epics vs stories vs tasks: is a sub-task the same as a task?
In tools like Jira, a sub-task is a task that belongs to a story. The idea is the same.
Epics vs stories vs tasks: what comes above an epic?
Teams often use initiatives or themes to group epics under a strategic objective.
Are epics, stories and tasks part of Scrum?
No. Scrum only defines the Product Backlog and its items; this hierarchy is a common practice for organising them.
Epics vs stories vs tasks: can a story exist without an epic?
Yes. Small, standalone stories do not need a parent epic.
Epics vs stories vs tasks: how many stories should an epic have?
There is no rule. Many epics have somewhere between a handful and a few dozen stories; if it has far more, consider splitting it.
Epics vs stories vs tasks: where do bugs fit?
Most teams treat a bug as a backlog item at story level, sometimes linked to an epic, and break it into tasks if needed.
Where do I track epics, stories and tasks?
In a backlog tool; see Agile tools and techniques and the tool comparison.