Project Management

Project Management Central

Please login or join to subscribe to this thread
in a portfolio, How do you manage interdependency between projects??
Im dealing with 33 project across the site, a lot of them with interdependencies ..
any tips to manage them? to comunicate between the PMs? and more importante comunicate plans/risks/issues across the project execution?
Sort By:
Page: 1 2 next>
Mario, how about splitting them by the Sponsor? It's easier to manage when you stack them up based on the person who is providing the money.

As for the communication and flow of information, unless you have privacy concerns, my suggestion would be to keep it visible to everyone.
...
1 reply by Mario Posadas
Jan 14, 2020 4:49 PM
Mario Posadas
...
thanks Murtaza for your answer, the issue is that all of them have different sponsor..
i was thinking in some kind of meeting to explain the project and private discussions between PM to align dependencies... but im not sure if this is the best way to identified them and communicate to the rest of the site..
Jan 14, 2020 4:40 PM
Replying to Murtaza Sheikh
...
Mario, how about splitting them by the Sponsor? It's easier to manage when you stack them up based on the person who is providing the money.

As for the communication and flow of information, unless you have privacy concerns, my suggestion would be to keep it visible to everyone.
thanks Murtaza for your answer, the issue is that all of them have different sponsor..
i was thinking in some kind of meeting to explain the project and private discussions between PM to align dependencies... but im not sure if this is the best way to identified them and communicate to the rest of the site..
Mario -

Start simple with a dependency table with all 33 projects in the rows and columns, and the cells being a description or pictogram of the dependency.

Another way to summarize it would be a dependency map showing the linkages between the projects (dependent/depending).

Kiron
...
1 reply by Mario Posadas
Jan 14, 2020 5:18 PM
Mario Posadas
...
thanks Kiron.. i like your proposal to show them in a map
after that, during the execution what do you think could help the PMs to communicate risks that could or not affect other project?
The key point is: what do you need to know as portfolio manager? That is the key. I am writting this because I understood that you are talking about portfolio. So, there is no problem to manage a great amount of projects. On the other side, if you are talking about portfolio you have to have programs, not projects, as the main component inside it. If you have only projects then something is uncorrect in your portfolio architecture.
...
1 reply by Mario Posadas
Jan 14, 2020 5:15 PM
Mario Posadas
...
thanks Sergio.. as one of my questions mention im trying to develop some meeting or tool to communicate this dependencies to the PMs.. unfortunately there is a big lack in communication between them so im trying to imagine the best way to avoid issues during the execution of projects/programas (as you mention) due to misunderstandings
Jan 14, 2020 5:12 PM
Replying to Sergio Luis Conte
...
The key point is: what do you need to know as portfolio manager? That is the key. I am writting this because I understood that you are talking about portfolio. So, there is no problem to manage a great amount of projects. On the other side, if you are talking about portfolio you have to have programs, not projects, as the main component inside it. If you have only projects then something is uncorrect in your portfolio architecture.
thanks Sergio.. as one of my questions mention im trying to develop some meeting or tool to communicate this dependencies to the PMs.. unfortunately there is a big lack in communication between them so im trying to imagine the best way to avoid issues during the execution of projects/programas (as you mention) due to misunderstandings
...
1 reply by Sergio Luis Conte
Jan 14, 2020 5:35 PM
Sergio Luis Conte
...
No problem. What you have to do is to avoid noise then create a well defined interface between all the architecture which usually is, from botton to top, project - program - portfolio. Each component must be a black box that will connect with the other through a well defined interface. The interface is just the data each component need to translate internally into information. Translate internally to information mean that somebody has made the enough stakeholder analysis to understand what is needed as information. With that on hand you will not have problems about communication. The amount of programs and projects that I have to consider really scares so I am writting about the solution I found in the practice and it is using by all my actual work place.
Jan 14, 2020 5:07 PM
Replying to Kiron Bondale
...
Mario -

Start simple with a dependency table with all 33 projects in the rows and columns, and the cells being a description or pictogram of the dependency.

Another way to summarize it would be a dependency map showing the linkages between the projects (dependent/depending).

Kiron
thanks Kiron.. i like your proposal to show them in a map
after that, during the execution what do you think could help the PMs to communicate risks that could or not affect other project?
...
2 replies by Keith Novak and Kiron Bondale
Jan 14, 2020 6:25 PM
Keith Novak
...
A simple tool you can use is called an N-squared chart, also called an NxN (N by N) or N^2. It’s a dependency matrix that shows not only a dependency, but the direction of influence as well. By placing all the elements on the diagonal rather than just the row and column headings, you can easily see that A drives a change to B instead of just that they are somehow related by depicting the direction of influence in a clockwise manner. Each dependency is numbered, and the details of the dependency are contained in a separate list.

I’ve used them to track the interfaces between hundreds of WBS items in-work by many different teams. They’re traditionally used to manage the physical or functional interfaces in systems engineering, but I have found them very useful for many things.

They can be a bit difficult to read in Excel once they get large, so I sometimes put them in a large format on an office wall and use different colored push-pins (red yellow green) if I want to depict the risk or the health.
Jan 15, 2020 7:55 AM
Kiron Bondale
...
This could be something added as a column in a risk register and then aggregated across the risk registers of the different projects to an overall portfolio level.

You could also have regular portfolio-level risk reviews where PMs get a chance to share cross-dependency risks and timing expectations.

Kiron
Jan 14, 2020 5:15 PM
Replying to Mario Posadas
...
thanks Sergio.. as one of my questions mention im trying to develop some meeting or tool to communicate this dependencies to the PMs.. unfortunately there is a big lack in communication between them so im trying to imagine the best way to avoid issues during the execution of projects/programas (as you mention) due to misunderstandings
No problem. What you have to do is to avoid noise then create a well defined interface between all the architecture which usually is, from botton to top, project - program - portfolio. Each component must be a black box that will connect with the other through a well defined interface. The interface is just the data each component need to translate internally into information. Translate internally to information mean that somebody has made the enough stakeholder analysis to understand what is needed as information. With that on hand you will not have problems about communication. The amount of programs and projects that I have to consider really scares so I am writting about the solution I found in the practice and it is using by all my actual work place.
Jan 14, 2020 5:18 PM
Replying to Mario Posadas
...
thanks Kiron.. i like your proposal to show them in a map
after that, during the execution what do you think could help the PMs to communicate risks that could or not affect other project?
A simple tool you can use is called an N-squared chart, also called an NxN (N by N) or N^2. It’s a dependency matrix that shows not only a dependency, but the direction of influence as well. By placing all the elements on the diagonal rather than just the row and column headings, you can easily see that A drives a change to B instead of just that they are somehow related by depicting the direction of influence in a clockwise manner. Each dependency is numbered, and the details of the dependency are contained in a separate list.

I’ve used them to track the interfaces between hundreds of WBS items in-work by many different teams. They’re traditionally used to manage the physical or functional interfaces in systems engineering, but I have found them very useful for many things.

They can be a bit difficult to read in Excel once they get large, so I sometimes put them in a large format on an office wall and use different colored push-pins (red yellow green) if I want to depict the risk or the health.
Mario,

on the tactical level, we established a biweekly meeting of all projects, each project could request from another and these requests were communicated, deadlocks identified. The whole thing was made transparent on a big wall with an NxN matrix.

See https://www.slideshare.net/walenta/a-3laye...-agile-projects
Jan 14, 2020 5:18 PM
Replying to Mario Posadas
...
thanks Kiron.. i like your proposal to show them in a map
after that, during the execution what do you think could help the PMs to communicate risks that could or not affect other project?
This could be something added as a column in a risk register and then aggregated across the risk registers of the different projects to an overall portfolio level.

You could also have regular portfolio-level risk reviews where PMs get a chance to share cross-dependency risks and timing expectations.

Kiron
Page: 1 2 next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Bad artists always admire each other's work."

- Oscar Wilde

ADVERTISEMENT

Sponsors