Please login or join to subscribe to this thread
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.
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..
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).
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.
after that, during the execution what do you think could help the PMs to communicate risks that could or not affect other project?
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.
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.
You could also have regular portfolio-level risk reviews where PMs get a chance to share cross-dependency risks and timing expectations.
Please login or join to reply