PMviz

Dependency Management

In PMviz terms, a dependency is something required by a part of the programme/portfolio structure (e.g. a project) to enable it to complete its objectives. The 'something' is usually either produced by another part of the programme/portfolio (internal dependency) or required from outside the programme/portfolio (external dependency).

Dependencies can be regarded as the 'input' to a particular programme/portfolio element, and the deliverables regarded as the 'output'. In a typical programme/portfolio the 'outputs' from some parts of the programme/portfolio and required as 'inputs' to other parts. PMviz allows these dependency links between the programme/portfolio elements to be created, tracked and reported, and notifies the dependent manager if a dependency is not likely to be delivered on time.

In PMviz, dependencies are set up for a particular programme/portfolio element by linking it to milestones being delivered by other programme/portfolio elements. It will then highlight those where the forecast date for delivering the dependency is after the 'required by' date - referred to as a 'dependency violation'.

Emails are used to keep relevant managers informed about the status of dependencies. For example: to notify managers when a dependency is placed on one of their milestones; to notify a dependent manager if an agreed dependency forecast date slips past the 'required by' date: to notify dependent managers when the dependency milestone is completed.

• < Prev
• Next >