Epic

An EPIC represents the business objectives of the project, serving as a comprehensive set of functional and complex steps taken to implement product capabilities. Each business goal (Epic) in the system has a business weight, representing the priority of business tasks in a numerical value. This weight is determined based on the importance of logically sequential relationships between all tasks in the project or the priority of task execution in each Product Increment (PI). The business weight influences the system's algorithms in distributing the order of task execution (planning and assigning performers to carry out technological tasks and defect fixes). It is on a scale from 1 to 10, where 10 indicates the highest priority.

For example, considering three business tasks:

• Gathering product information - Business weight: 3
• Analyzing gathered information - Business weight: 2
• Market analysis - Business weight: 2
• Creating specifications for developers - Business weight: 1

Or, assuming that market analysis has a higher priority than gathering information, the business weights would be:

• Market analysis - Business weight: 4
• Gathering product information - Business weight: 3
• Analyzing gathered information - Business weight: 2
• Creating specifications for developers - Business weight: 1

Tasks (tasks) with higher business weight in Epics are prioritized in the planning algorithm.

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 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) on the Epics and Detail Epic screens.

User Actions:

• Creation, editing (name, description, business weight) at any time.
• Moving to another Capability.
• Linking and changing the link with Product Increment.
• Decomposition at any time.
• Deletion is possible if the Epic is not decomposed into Solution Items.