Flocci Projects

Home › Agile answers › What is the difference between an epic, a story and a task?

What is the difference between an epic, a story and a task?

An epic is a large outcome spanning several sprints. A story is a user-visible slice that fits in one sprint and can be demonstrated. A task is a unit of work with no independent user value — a step toward a story. The test is demonstrability: if you cannot demo it, it is a task.

The demo test

Ask what you would show at a sprint review. 'Users can reset their password by email' is a story — you can demonstrate it. 'Add the password_reset_tokens table' is a task, because showing a migration to a stakeholder communicates nothing. 'Self-service account management' is an epic: it is several demos over several sprints.

A worked example

Epic: checkout revamp. Stories: user can pay with UPI; user can save a card; user sees a receipt by email. Tasks under the UPI story: integrate the gateway SDK, handle the callback, add failure retries. Points go on the stories; the epic's size is their sum; tasks may be left unpointed as implementation detail.

Where teams go wrong

The common failure is a backlog of tasks with no stories, which makes the board look busy while nobody can say what the user gained this sprint. The opposite failure — everything is a story — produces eight-point 'stories' that are really epics and never finish inside a sprint.

How Flocci Projects models it

Five types: Epic for the arc, Feature and Improvement for user-visible slices, Task for implementation steps, and Bug for defects. Issues roll up to an Epic, sprints are scoped from the child issues, and the type filter lets you look at the board through any one of these lenses.

Try it on a free Flocci Projects board

Related questions

Do tasks need story points?

Usually not. Point the story that the tasks belong to, so velocity stays a measure of delivered user value. Pointing both double-counts and inflates velocity without adding forecasting accuracy.

Can a bug be a story?

A bug is its own type because its origin and triage differ, but at sprint-planning time it competes for the same capacity as a story. Whether you point bugs is a team convention — just apply it consistently.

How many stories should an epic contain?

Enough that each is demoable and few enough that the epic closes within a quarter — in practice, roughly five to fifteen. If you are past twenty, it is an initiative and should be split into several epics.

More agile answers