Home / Features / Types of Dependency

Types of Dependency

Collaborate with other projects instead of competing with them

"You first"... "No you"

In a multi project environment, it’s important to be clear about who is delivering what, and when.

Portfolio Manager lets modellers work independently in the same model, but with visibility of the other changes being worked on. Performing impact analyses, reveals dependencies between work on individual elements, which can be traced back to projects.

The types of project dependency made explicit are:

  1. Co-dependency. This is where two projects have branched the same elements so are thinking about making changes which may interfere with each other, but neither has any firm plans…yet. Shown here between C1 and C2
  2. Direct dependency. Project C3 is planning a change to some elements, and Project C2 is branching from those planned elements (i.e. Project C2 requires Project C3 to deliver) then Project C2 has a direct dependency on Project C3.

Click on a link to see the detail of which elements are creating that dependency.

So what?

Once dependencies have been identified, the project managers involved can meet to discuss the risks to each of them, figure out mitigations, or escalate the issues.

The main thing is that these conversations can happen early, not just when the changes are about to be merged or implemented – eliminating redundant work and wasted time, producing better results for everyone.

For more information see the Help article Project dependency diagram

More features like this

Pricing and features

Find out what’s included…

Check out Pricing

Download Portfolio Manager

Take a free, no obligation, 30-day trial today. Discover for yourself the difference that Portfolio Manager real-time impact analysis will make to your EA modelling.

Download