What is an epic in agile methodology?
In agile project management, an epic is a large functional block representing a high-level user goal. Too large to fit in a single sprint, an epic is broken down into several user stories that will be planned and developed progressively over multiple iterations.
Unlike user stories that address a specific and immediately testable need, an epic provides strategic direction. It's the vision before the detail. In Scrum, epics live in the product backlog and serve as containers to organize stories before they are refined.
The word "epic" comes from comic book culture: an epic is a large saga spanning multiple issues. In agile, it's the same idea — a large feature that unfolds across multiple sprints.
Epic, user story, task: understanding the agile hierarchy
The agile method organizes work in decreasing levels of granularity. Each level answers a different question:
Initiative / Theme
The highest level — a business or strategic goal. E.g., 'Improve mobile experience'.
Epic
A large functional goal lasting multiple sprints. E.g., 'iOS mobile app redesign'.
User Story
A specific feature from the user's perspective. E.g., 'As a user, I want to receive push notifications'.
Task / Subtask
Technical work to implement a story. E.g., 'Integrate Firebase Cloud Messaging API'.
Concrete examples of agile epics
SaaS / Product
- Authentication system (SSO, 2FA)
- Analytics dashboard
- Subscription and payment management
- User onboarding module
E-commerce
- Optimized checkout funnel
- Loyalty program
- Returns and refunds management
- Product catalog with advanced filters
Mobile app
- Personalized push notifications
- Offline mode
- Integrated social sharing
- Interactive onboarding
Internal project
- Cloud migration
- HR intranet redesign
- Report automation
- CRM/ERP integration
How to define and break down an epic?
Write the goal in user language
Frame the epic from the end user's perspective: 'Users can manage their subscription from A to Z without contacting support'. Avoid technical jargon at this stage.
Define acceptance criteria
List the conditions that will allow the epic to be considered complete. These criteria will guide the breakdown into user stories and validation testing.
Estimate size (T-shirt sizing)
Before breaking down, estimate the overall size: XS, S, M, L, XL. If your epic is XL, consider subdividing it into sub-epics. This step takes 30 minutes maximum as a team.
Break into INVEST user stories
Each user story from the epic must be Independent, Negotiable, Valuable, Estimable, Small and Testable. If a story doesn't pass the INVEST filter, break it down further.
Prioritize and plan
Rank stories by value/risk and plan the most important ones into upcoming sprints. The epic stays in the backlog until all its stories are complete.
Which tool for managing agile epics?
Not all agile tools are equal when it comes to managing epics. Jira is the historical reference but its complexity and price (from $7.75/user/month) make it difficult to access. monday.com doesn't have native agile hierarchy (epic → story → task) and requires workarounds.
Epics, sprints and stories in Tandimy
Create your epics, break them into stories and plan your sprints — all in one tool. Free to start.
Pro tip: regardless of the tool, consistency is most important. Choose an epic/story/task structure and stick to it throughout the project. Changing hierarchy mid-project costs more than starting wrong.
FAQ
Manage your epics and sprints with Tandimy
Backlog, epics, sprints, kanban — everything an agile team needs, without Jira's complexity.