Connections

In the context of Business Management, it is apparent that in the same company, a large number of projects are interrelated.

We can distinguish the following user cases:

  • Projects can share a common objective and be part of the same Program.

  • A project follows a specific process during which it goes through a series of different states (i.e., Natures).

  • A project can be made up of sub-projects (a.k.a. Work packages); hence it can have a  hierarchical structure.

  • Interrelated projects share some common aspects (deliverables, finances, etc.) through Contracts.

  • If projects are interrelated, they have an actual impact on each other’s schedules that can be managed with Dependencies.

Sciforma provides all the tools necessary to deal with the varied project scenarios.

Sciforma offers three types of connections:

Connections_types.png
  1. Life cycle connections – Connect objects that have a common life cycle (but no contract).

    For instance, a Business Case could become a Project at the end of its workflow.

  2. Intra-Nature connections – Connect two projects of the same Nature.

    For instance, a Project A Task could constraint the start of a Project B Task. In that case, a Dependency will be created.

  3. Hierarchical connections – Define the structure and hierarchy that exists between the different Natures of projects that share the same overall goals.

    For instance, Products and Projects that are embedded in a Program. In that case, Dependencies will be created. In addition, Contracts can also be created in order to better manage Time Frames, Deliverables, and Budgets.

Settings

The possibility to create some connections depends on the options that are activated by the Administrator in the System Settings workspace, Project Settings folder, Global Options tab, Connections sub-tab.

Life Cycle Connections

Life cycle Connections allow the user to link together various objects that are connected through a process (a Business Case that is turned into a Product, for instance). This makes the overview easier to navigate and facilitates the tracking of related elements by going back and forth between the elements.

It is possible, for example, to have the same Scoring template between the two connected objects.

Life_Cycle_Connections.png

The direction of the arrows indicates the direction of the connections: from the “Source” object to the “Target” object. The N-N is a term used to denote a many-to-many relationship (N objects on one side are related to N objects on the opposite side).

Important

Connections are always created from the “Source” object to the “Target” object. The editing and/or deleting of connections will have to be done at the “Source” level. Connections at the “Target” level will be read-only.

Connections can be created in two different ways:

  • The “Target” object can be created automatically from the “Source” object.

  • The “Source” object can be connected to an already existing “Target” object.

If desired, an Idea (“Source” object) can be connected to:

  • One or many Business Cases (“Target” objects).

  • One or many Products (“Target” objects).

  • One or many Projects (“Target” objects).

  • One or many Programs (“Target” objects).

If the Business Case (“Source” object) aligns with the company’s strategic objectives and its capacity to deliver, the Business case can then be connected to:

  • One or many Products (“Target” objects).

  • One or many Projects (“Target” objects).

Intra-Nature Connections

Intra-Nature connections allow users to link together related projects that share the same Nature.

There is still a “Source” and “Target” logic in this case; the connection can only be edited from the Source object. The aim is to facilitate the overview and the tracking of related elements by going back and forth between the elements.

The Contract represents the terms agreed upon by the “Source object” manager and the person in charge of the connected object with respect to the timeframe, budget, and deliverables.

The following natures accommodate Intra-Nature connections: Project, Product, Program, and Business Case.

Hierarchical Connections

Connections can also be used to define the structure and hierarchy between the different Natures of projects that share the same overall goals (For instance, when managing a program containing several projects and products).

Hierarchical Connections allow the user to add a Contract between the interconnected objects if needed. Apart from facilitating the overview and the tracking of related elements by going back and forth between the elements, connections with contracts provide the opportunity to manage deliverables, changes, and the budget.

Hierarchical connections allow the user to:

  • Link projects of different natures with some common points (no Contract).

  • Link projects with some aspects (Budget, Deliverables, Timeframe) agreed upon between the Managers (with a Contract).

    Note

    Only hierarchical connections can have a Contract.

Hierarchical connections in Sciforma can be illustrated as follows:

Hierarchical_Connections.png

The direction of the arrows indicates the direction of the connections: from the “Source” object to the “Target” object. The N-N is a term used to denote a many-to-many relationship (N objects on one side are related to N objects on the opposite side). The term 1-N refers to a one-to-many relationship (1 object on one side is related to objects on the other side).

Important

Connections are always created from the “Source” object to the “Target” object. The editing and/or deleting of connections will have to be done at the “Source” level. Connections at the “Target” level will be read-only.

The Contract represents the terms agreed upon by the “Source object” manager and the person in charge of the connected object with respect to the timeframe, budget, and deliverables.

Note

The Work Package contract is different from other contracts, as it comes with a Contract Changes feature. This allows the Work Package Manager to formally ask the Project Manager for contract modifications to be made when the contract is locked. Moreover, the connection is automatically created when creating work packages.

Connections can be created in different ways:

  • The “Target” object can be created automatically from the “Source” object.

  • The “Source” object can be connected to an already existing “Target” object:

    • When using the connection feature, and

    • When creating a Dependency from the Target object to the Source object.

If managed, Programs (“Source” object) can have a hierarchy connection with:

  • One or many Business Cases (“Target” objects),

  • One or many Projects (“Target” objects),

  • One or many Products (“Target” objects) and

  • One or many Work Packages (“Target” objects).

If managed, Business cases (“Source” object) can have a hierarchy connection with:

  • One or many Work Packages (“Target” objects).

If managed, Products (“Source” object) can have a hierarchy connection with:

  • One or many Projects (“Target” objects),

  • One or many Work Packages (“Target” objects).

If managed, Projects (“Source” object) can have a hierarchy connection with:

  • One or many Work Packages (“Target” objects).

Settings

The possibility to create some connections depends on the options that are activated by the Administrator in the System Settings workspace, Project Settings folder, Global Options tab, Connections sub-tab.

In this section