Add Your Heading Text Here
Epic
In Azure DevOps, an epic is the highest level of work item, representing a large body of work that spans multiple features and often several months. Epics capture a major goal or initiative, then get broken down into features and user stories, giving teams a way to plan and track big-picture progress.
What it means
An epic is deliberately broad. It answers 'what large outcome are we going after' without pinning down every detail up front. Because it can take a quarter or more to deliver, an epic is rarely worked on directly. Instead it acts as an umbrella that features and stories hang from, so a team can see how a big initiative is progressing without drowning in individual tasks.
In requirements terms, an epic is where a high-level need enters the backlog before it is refined into something buildable. Tracing a requirement up to its epic shows why the work exists and which strategic goal it serves. Keep epics genuinely large and few in number. If everything is an epic, the level stops carrying any useful meaning.
In practice
A fintech team creates an epic called 'meet new open banking regulations'. Under it sit features for consent management, data sharing, and audit logging, and under those sit the individual user stories. The epic gives leadership one thing to track, while the teams work several levels down.
Foire aux questions
What is the difference between an epic and a feature in Azure DevOps?
How big should an epic be?
Manage requirements the modern way
Modern Requirements brings documentation, traceability, and reviews together inside Azure DevOps.
