Share this page

# Epics

Epics can be workspace-specific or shared.

You can create shared epics in workspaces that are members of the shared space. Shared epics are inherited by all the workspaces in the shared space.

Note: Creating or modifying shared epics requires space admin permissions. Other members of the shared space have read-only permissions.

The following table summarizes the characteristics of shared epics.

Feature | Details
--- | ---
Business rules | Only shared business rules apply to shared epics.
Fields | In shared epics, you can only define shared fields. Values set in the shared fields are reflected in all the workspaces. Note: In shared reference fields, such as Milestone, Release, and any shared user-defined fields, only shared items can be selected. The following fields are not available in shared epics: Owner, User tags, Waste, Waste category, Repeated phase, Requirements
Comments | Comments that are added to a shared epic in one of the workspaces are not available in the other workspaces.
Related items | A shared epic can have different related items in each workspace.
Convert | You cannot convert a shared epic to another entity type.
Follow | You cannot follow shared epics.
Bulk update | In a single bulk-update operation, you can only update epics that are either shared or isolated. You cannot bulk update epics of different types in the same operation.
Sequential ranking | Shared epics can only be ranked separately from isolated epics.
History | Changes to the shared epic fields are reflected in the epic's history.
Attachments | Attachments of shared epics are shared.

Back to top

## Define epic business values

You can track the perceived and actual business values of epics. This helps you prioritize epics based on the value they deliver, and determine the gap between the initial and final estimation of an epic.

Epic value definition

An epic value is based on several factors, such as customer value, commercial value, market value, efficiency value, and future value.

The epic value definition depends on the methodology adopted by the product team, and may vary across teams.

You can define an epic value in two stages.

Value | Description
--- | ---
Perceived value | The epic's initial value estimation that helps prioritize the epic relative to others. The perceived value is estimated by the product team when creating an epic and determining its business priority. Tip: The perceived value score should justify an epic's priority over other epics.
Actual value | The epic's true value, as concluded after the implementation and delivery of the epic. The actual value score is calculated by the product team to track the value gap for different epics over time. Note: Define the actual value in the epic details after the epic’s implementation.

After the epic actual value is defined, the value gap is automatically calculated. The value gap is the difference between the perceived and actual values of an epic.

Note:

- You can edit the perceived and actual value scores in any phase of an epic. The value gap is automatically recalculated.
- You can use decimal numbers for value scores.
- Your admin can set the minimum and maximum value scores with the help of a business rule. For example: The perceived value field should be between 1 and 100. For details, see Design business rules.

Back to top

See also:

- Build the backlog
- Execute a release
- Quality

https://admhelp.microfocus.com Software Delivery Management 8942
Tips to improve your search results... OpenText™ Software Delivery Management Help Center OpenText™ Software Delivery Management Help 26.1 All View Local Help Center View Online Help Center Version: