--- title: Create an epic in Agile Development 2.0 description: Define the high-level requirements of the features that you want to develop by creating epics in Agile Development 2.0. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-business-management/agile-development/create-an-epic.html release: australia product: Agile Development classification: agile-development topic_type: task last_updated: "2026-03-12" reading_time_minutes: 4 breadcrumb: [Managing your product development using Agile Development 2.0, Agile Development 2.0, Agile Development, Strategic Portfolio Management] --- # Create an epic in Agile Development 2.0 Define the high-level requirements of the features that you want to develop by creating epics in Agile Development 2.0. ## Before you begin Role required: scrum\_story\_creator, scrum\_admin ## About this task Create epics in Agile Development 2.0 and organize them in a hierarchy of parent and children. You can associate an epic to a product, theme, or configuration item \(an item or service that is affected\). ## Procedure 1. Navigate to **Agile Development** > **Epics**. 2. Select **New**. Alternatively, you can open the new epic form using the Agile board, from a theme record, or from a product record. You can also convert an existing active story into an epic. For details, see [Related links and lists for a Story in Agile Development 2.0](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/agile-development/agile-2-0-story-related-lists-related-links.md). 3. On the form, fill in the fields.
| Field | Description |
|---|---|
| Number | System-generated number for the epic. |
| Product | Product associated with this epic.You can associate an epic with only one product at a time. |
| Priority | Priority of the epic. |
| State | State of the epic. Select one of the following:- **Draft** The epic requirements, such as the detailed description, are still being drafted. - **Ready** The epic is ready for pickup by the product team. The product manager and the scrum team can break the epic down into stories. - **Work in Progress** The development team is working on the stories for epic and recording the changes in the work notes field. - **Complete** The development and testing efforts on all the stories and any child epics for the epic are complete. - **Cancelled** The epic has been canceled. This field is automatically set to **Draft**. |
| Short Description | Brief description of the epic. |
| Description | Detailed description of the epic. |
| Work notes | Notes about the work done on the epic. |
| Total story count | Number of stories in the epic. |
| Completed count | Number of completed stories in the epic. |
| Percent complete by count | Percentage of completed work in the epic. Story count is used to calculate this value. |
| Total estimate | Sum of the estimates of all stories in the epic. |
| Completed estimate | Sum of the estimates of all the completed stories in the epic. |
| Percent complete by epic | Percentage of completed work in the epic. Story estimate is used to calculate this value. |
| Missing estimate | Number of stories in the epic that are missing estimates. |
| Top program | Program mapped to the scrum work enabling top-down hybrid planning.This field is visible in the Scrum view of the epic form if you activate the PPM Standard plugin \(com.snc.financial\_planning\_pmo\). |