Epic

Is a set of functional and complex steps taken to achieve broader company goals. It can be decomposed into the result of purposeful work performed within a specific set of technical tasks (Solution Items).

Each business goal (Epic) in the QPM system has a business weight.

Business weight of Epic is the priority of business tasks expressed in a numerical value. It is determined depending on the significance of logically sequential relationships in executing all work in the project or the priority of executing business tasks in each PI.

It affects the QPM system's algorithms in distributing the order of work execution (planning and assigning performers to perform technological tasks).

The scale ranges from 1 to 10, with 10 being the highest priority.

For example, there are three business goals:

1. Gathering information about the product
2. Market analysis
3. Analysis of collected information
4. Drawing up specifications for developers

Accordingly, they have the following priorities or business weight:

Gathering information about the product - 3

Analysis of collected information - 2

Market analysis - 2

Drawing up specifications for developers - 1

Alternatively, if we assume that Market analysis has a higher priority than Gathering information about the product, then the business weight of my Epics would be as follows:

Market analysis - 4

Gathering information about the product - 3

Analysis of collected information - 2

Drawing up specifications for developers - 1

Tasks associated with Epics with higher business weight are given priority in the planning algorithm.

Statuses:

• Not defined: There is no Solution Item
• Awaiting: If all Solution Items are in the Awaiting status, it means the work is entirely dependent on the work in another epic.
• In progress: At least one Solution Item is in progress.
• Done: All Solution Items are done.

Linking Epic and Product Increment

An Epic, as a business goal or task, must be implemented by a certain completion date. Establishing a link with Product Increment essentially determines the epic's realization date. The link with Product Increment is not a mandatory condition and can be created, modified, or terminated at any time during product or project development.

Rules for Changing the Link Between Epic and Product Increment

The QPM system imposes no restrictions on the link between Epic and Product Increment based on the status of the Product Increment. If an Epic is decomposed at the time of transfer:

• Decomposed to the Solution Item level
• Decomposed to the Task level

Transfer between projects:

• If an Epic is decomposed and has a link to an increment located in a project with the statuses "completed" or "on hold," its transfer is not possible. The user must change the project status to "Active" before proceeding with the transfer.
• Transfer between projects in different statuses is allowed according to the previous rules.

Breaking the Link:

An Epic can be detached from the increment at any time. If the Epic is decomposed into Solution Items:

• Decomposition is preserved and visually displayed on the Epic Detail page.
• Data of decomposition elements remain unchanged.
• All links between Solution Items remain unchanged.
• The link between Solution Item and Team remains unchanged.
• All links between tasks remain unchanged.
• If there are tasks in the Epic in the To Do, Doing, Review stages, they are removed from the stages, assignments are canceled. Tasks in Done remain in Done.
• Data of all decomposition elements can be edited.

Tasks will be back in progress when a link is established with Product Increment, and that Product Increment is either defined or transitions into that status over time.

Decomposition:

It can be broken down into the result of purposeful work by a team within a specific set of technical tasks (Solution Item)

The user has the ability to automate the creation of Solution Items - creating a pipeline for each Epic. The connection between Epic and Pipeline is established through the belonging of the Epic to a certain category

User actions:

• Editing Epics (name, description, business weight) at any time. 
• Linking and changing the link with Product Increment.
• Decomposition at any time
• The determination of belonging to a category (the association between Epic category and Pipeline defines the automatic creation of a chain of Solution Items, according to the created Pipelines - a specific sequence of team tasks)
• Deletion is possible only if the Epic is not decomposed into Solution Items.