Flocci Projects

HomeAgile answers › What is an epic in agile project management?

What is an epic in agile project management?

An epic is a body of work too large for one sprint, broken into smaller stories that each deliver a testable slice. Epics group related stories so progress rolls up — 'payments revamp: 7 of 12 done' — giving stakeholders altitude while the team works at story level.

The hierarchy that matters

Epic, then stories, then optionally tasks. A story fits in a sprint and delivers user-visible value; an epic is the narrative arc those stories belong to. If a story cannot finish inside one sprint, it is an epic wearing a disguise and it needs splitting.

How to split an epic

Slice vertically by user value, not horizontally by layer: 'user can pay with UPI', then 'user can save a card' — never 'build the database' then 'build the API'. Each slice should be demoable alone. The classic patterns are by workflow step, by user type, by happy-path-first, and by CRUD operation.

Epics on the board

In Flocci Projects, Epic is one of five issue types alongside Task, Bug, Feature and Improvement, and related issues roll up to it, so the board shows the individual work moving while the epic shows the arc completing. Sprint planning pulls the child issues, never the raw epic.

Try it on a free Flocci Projects board

Related questions

How big should an epic be?

Typically two to six sprints of stories. Beyond that it is really an initiative and should be split into multiple epics with independently meaningful outcomes, or nobody will ever see it finish.

Do epics get story points?

No — point the stories, and the epic's size is their sum. Pointing an epic directly is guessing with extra steps, and the guess will be wrong in a direction nobody can audit.

When should I close an epic?

When its outcome is achieved, even if nice-to-have stories remain — move those to the backlog as standalone items. Epics that never close stop meaning anything, and a board full of eternal epics is a board nobody reads.

More agile answers