Definition
Epic
An epic is a large unit of work too big to finish in a single cycle, broken down into smaller related issues that ship incrementally. It groups those child issues under one theme and tracks their combined progress. Epics sit between individual issues and broader projects or initiatives in the planning hierarchy.
Key takeaways
- An epic is a large unit of work too big to finish in a single cycle, broken down into smaller related issues that ship incrementally. It groups those child issues under one theme and tracks their combined progress. Epics sit between individual issues and broader projects or initiatives in the planning hierarchy.
- Some work is simply too large to be one issue — a new onboarding flow, a billing rewrite, a search overhaul.
- In Planoda, issues can be grouped under a parent so an epic's progress reflects the live state of its children automatically, bridging day-to-day issues and roadmap-level initiatives.
Some work is simply too large to be one issue — a new onboarding flow, a billing rewrite, a search overhaul. An epic is the container for that work: a parent that holds many child issues, each small enough to estimate, assign, and complete on its own. The epic exists so the big picture stays coherent while the actual work happens in shippable pieces.
Epics earn their keep through roll-up. Rather than reconstructing 'how far along is the search overhaul' from a dozen scattered issues, you read the epic, which aggregates the state of its children into a single progress view. This gives stakeholders a meaningful altitude — bigger than a task, smaller than a quarter-long initiative — to track without drowning in detail.
The discipline is decomposition. An epic whose children are themselves enormous is just a project in disguise; an epic with no children is a bloated issue. The sweet spot is a theme that spans a few cycles and breaks cleanly into a handful of independently deliverable issues.
In Planoda, issues can be grouped under a parent so an epic's progress reflects the live state of its children automatically, bridging day-to-day issues and roadmap-level initiatives.
Related terms
- InitiativeAn initiative is a large, strategic body of work that spans multiple projects, teams, or cycles toward a single outcome. It sits above projects and issues in the planning hierarchy, grouping related efforts under one goal. Initiatives let leadership track progress on big bets without drowning in individual tickets.
- ProjectA project is a bounded body of work with a defined goal, scope, and usually an end date — a feature launch, a migration, a redesign. It groups the related issues that deliver that outcome, sitting above individual issues and below strategic initiatives in the planning hierarchy, so a team can track one cohesive effort as a unit.
- RoadmapA roadmap is a high-level, time-oriented view of what a team or product plans to build and roughly when. It communicates direction and sequencing across initiatives and projects, aligning stakeholders on priorities. Unlike a backlog of granular tasks, a roadmap operates at the altitude of themes, outcomes, and quarters rather than individual issues.
- BacklogA backlog is the ordered list of all work a team has identified but not yet started — features, bugs, improvements, and ideas. It is the team's single source of pending work, prioritized so the most valuable or urgent items sit at the top, ready to be pulled into a cycle or onto a board.
- Story Points (Estimation)Story points are a relative, unitless measure of how much effort an issue will take, accounting for complexity and uncertainty rather than raw hours. Teams estimate in points — often using a Fibonacci-like scale — to compare items against each other quickly. Summed across a cycle, points feed velocity and burndown without false precision about clock time.