Search results
Agile Epics: Definition, Examples, & Templates. An epic is a large body of work that can be broken down into a number of smaller stories. Learn more about how to organize an agile workflow with epics. Read this article
- User Stories
Summary: A user story is an informal, general explanation of...
- User Stories
This tutorial will explain how to use epics in agile software development with Jira. It will focus on epics in company-managed and team-managed projects.
16 maj 2023 · Epics. Epics represent either topics or overriding goals, which are then broken down into Stories and Tasks. An Epic could present the theme/topic to which a task belongs or represent a big project, for example “Migration customer X” in consulting or “Website Relaunch” in marketing.
An epic is a large body of work that can be broken down into a number of smaller stories, or sometimes called “Issues” in Jira. Epics often encompass multiple teams, on multiple projects, and can even be tracked on multiple boards. Epics are almost always delivered over a set of sprints.
An epic captures a large body of work—performance-related work, for example—in a release. It's essentially a large user story that can be broken down into a number of smaller stories. An epic can span more than one project, if multiple projects are included in the board where the epic is created.
In Jira, an epic is an issue type that represents a high-level initiative. It’s a large body of work that can be broken down into smaller, more manageable parts. Epics are also useful for grouping similar or recurring work.
Epics help organisations break their work down, organise that work, while continuing to work towards a bigger goal. In a sense, epics in agile are similar to epics in film or literature. Epics can be broken down into specific pieces of work, called Features.
