Epic
An epic is a large body of work that is divided into smaller user stories or tasks for implementation across multiple iterations.
“A large user story that cannot be delivered as defined within a single iteration or is large enough that it can be split into smaller user stories.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Epic?
Epics help organize major business features that cannot be completed within a single sprint and provide a high-level view of product development.
Large feature: Represents significant business functionality.
Decomposition: Broken down into manageable user stories.
Agile planning: Supports roadmap and release planning.
Real World Example
A regulated product team is preparing a release where Epic appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Epic as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Epic and similar ideas.
The page becomes useful in practice because Epic is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Epic in the context of ISTQB terminology?
Question 2
A tester needs to explain Epic to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Epic. Test your understanding with topic-specific questions in our Mock Exams.