Pascal DelaporteProjects Manager| BRGMFleury-Les-Aubrais, France
I am looking for a template or strategy to follow / classify the dependencies between projects : Some projects can have linked deliverables, one depending on the other. Is there a way to record and follow closely these dependencies ? Saving Changes...
Really depends what you want to do with this dependency map. If it is to understand the cascading impacts of delays in one project on another, a scheduling tool (e.g. MS Project or Oracle Primavera) would be needed.
If it is merely to understand the relationship (unidirectional, bidirectional), then a simple spreadsheet would do the trick with the list of projects in both the columns and rows and each cell representing the dependency between the projects.
You could also have a halfway solution between these two using a drawing or whiteboard tool where each project is represented as a box with arrows indicating the dependencies on other projects.
Kiron Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Pascal
documenting the dependencies is a good idea, since you have several PMs involved who cannot work independently, but have to satisfy external relationships, from their individual view. The PMs have to communicate about this, I have seen it done by dependency matrices and regular meetings.
If you have many dependencies consider to create a program and the PgM will be in charge of integration. Since deliverables are related to benefits, and benefits management is one of 4 program domains, it is about ensuring benefits are created by not a single project but the program itself.
Kiron is right, dependencies of deliverables will result in schedule dependencies, resourcing dependencies, and much alignment on e.g. quality standards, handover, communication and documentation. A PgM would take care of this. Saving Changes...
Often that is done on what is known as a Master Phasing Plan, Master Plan, Integrated Master Plan, or other similar terminology. Many examples are available online. That is a graphical schedule view.
Another method is to use a matrix such as an N by N (N-squared) diagram which allows you not only to depict dependencies, but also describe them and show the direction of dependency (A provides input to B). Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
I've worked in a program management office where the dependencies were put right into the project schedules. (We were using Microsoft Project Server to manage all the projects.)
In my last project, it was much simpler: dependencies, along with constraints, were tracked in their own registry. The problem with this approach is that each end of the dependency have to track it. Saving Changes...
Latha Thamma reddiSr Product and Portfolio Management (Automation Innovation)| DXC TechnologyMckinney, Tx, United States
Thanks for sharing. Saving Changes...
Ahmed EmaraFounder & CEO| innovation CloudRiyadh, Riyadh, Saudi Arabia
I would suggest to create like Dependency Matrix Map this will help you to under stand the interferences and come with common dependency within the projects Saving Changes...
