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.

  3. On the form, fill in the fields.
    Table 1. Epic form
    FieldDescription
    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 story requirements, such as the description and acceptance criteria, are still being drafted.
    Ready
    The story is ready for pickup by the development team.
    Work in Progress
    The development team is working on the story and recording the changes in the work notes field.
    Complete
    The development and testing efforts on the story are complete.
    Cancelled
    The story 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).

    Fill in the Planning section if you want to create benefit plans for the epic. This section is available in the Benefit view of the epic form.

  4. Click Submit.

What to do next

Add child epics or stories to the epic:
  • Create a child epic for this epic by selecting New from the Child Epics related list.
  • Add stories to this epic by selecting New from the Stories related list. For more information, see Create a story in Agile Development 2.0.

    An epic can have one or more stories, but a story can belong to only one epic at a time.