This section explains how to add epics and how to have them executed by agile projects.
Note: The Epics tab is available only when it is enabled. For details, see Set up portfolio tabs.
Overview of epics
Epics are containers that capture and manage agile initiatives. Portfolio epics are the agile practices at the enterprise scale. A portfolio epic probably requires different agile teams to implement. The agile teams run agile projects in different agile tools for the epic implementation.
Currently, PPM supports portfolio epics to be implemented by agile projects that are run in ALM Octane and Atlassian JIRA only.
- Prerequisite: Make sure the parameter
SHOW_PORTFOLIO_EPICS_IN_PORTFOLIOis enabled to show the Portfolio Epics tab.
- Open the portfolio.
- In the Portfolio Epics tab, click Add Epic.
- Enter the name, description, and owner for the epic.
- Click Add to add the epic or click Add & Another to add another one.
To edit the epic, click the epic link to open the details page and change the epic attributes.
Portfolio epics should process through various states of maturity until they are approved for implementation.
|Funnel||The capture state|
|Review||Preliminary estimates, including opportunity, effort, and risk.|
|Analysis||Establish viability, outcomes, development, and development impact.|
|Portfolio Backlog||Epics with "go" approval.|
|Implementation||Epics being implemented by projects.|
When an epic is approved for implementation, you relate the epic with an agile project, where the epic will be added and implemented.
- Your administrator has prepared an agile environment for portfolio epics. See
Configurations for Portfolio Epics.
- In the Portfolio Epics tab, click the epic to be implemented.
- In the Relations with Agile Projects section, click Add Relation.
Follow the instructions in the Add Relation with Agile Project window.
When the process is completed, you can see a related epic is added in the Relations with Agile Projects section.
You may relate the same portfolio epic with several agile projects, if it requires cooperation among the projects.
Field Description Related Epic
Epic that is added and implemented in the related agile project.
To view the epic details in the agile project, click the related epic name.
Note: Initially, the related epic has the same name as the portfolio epic. The agile project manager may later change the name or split the epic into smaller items during implementation.
Agile Project Where the portfolio epic is added and implemented. Progress How much the related epic is completed. Story Points Story points required for the agile project to complete the related epic. Agile Instance Agile environment that your administrator prepared for PPM to communicate with the agile project. Agile Product Agile system where the agile project is run. Last Updated Date Date when the related epic information is last synchronized from the agile project to PPM.
PPM periodically syncs from the related agile projects the actual progress information of each related epic.
The progress of the portfolio epic depends on the progress of each related epic:
- Total story points: sum of story points of each related epic
- Overall progress: sum of (story points of each related epic * progress of each related epic) / total story points
How story points and progress of related epics in agile projects are calculated
In ALM Octane
Related epic's story points = sum of (story points of all the backlog items that belong to the epic)
Progress = story points of Done backlog items / sum of (story points of all the backlog items that belong to the epic)
Related epic's story points = sum of (story points of all the issues that belong to the epic)
Progress= story points of Done issues / sum of (story points of all the issues that belong to the epic)
Note: Story points of sub-tasks are not included.