Dear all, I just created this generic post about managing project portfolios [1], but I want to clarify some details on how Spider is designed to use it, as I think it is well thought through in Spider.
In my understanding that it the cycle is like this:
1) Individual project schedules are built
2) Project portfolio, which contains 2 or more projects is created
3) Individual projects are consolidated into portfolio
4) Dependencies are added between projects in portfolio
5) Portfolio is scheduled
6) Portfolio is distributed to a new version of a projects
7) Individual schedulers start working with individual projects
In this stage the scheduler can update progress etc, but also is able to re-schedule the project with the option As a part of project portfolio In another words the scheduler can re-schedule the project as if other projects do not change (which is logical)
Question: is there any way at this stage for a scheduler of individual project to see what external dependencies drive his project?
8) at cetrain moment a portfolio is consolidated again and the whole cycle repeats from the step 5. I guess at this stage someone like a program/portfolio manager assesses impact on the overall schedule as well as on the individual schedules, resolves the conflicts, take decisions on priorities and approves a new master schedule.
Is this how it is meant to work in Spider?