L
Linda
I was wondering if it was dangerous (or even possible) to set up a master
project on MS Project Server 2003 if the master project consisted strictly of
milestones that are linked to other milestones from within other projects on
the same server.
I want the milestones in the other projects, as they are completed, to
update the milestones in the master project.
Or--am I making this too complicated? Should I make the master project
consist of the milestones from the other projects? In doing so would I be
causing issues if I published the Master Project on the server since the
master would consist strictly of milestones that do not have assigned
resources?
Would I be making issues worse if the milestones in the other projects were
themselves updated from "sub" projects (knowing that I would have to open and
update each project plan in the correct order, lower to higher, to be sure
the high-level plan is accurate?)
I have already referenced the "How to link tasks in a project across
projects." My projects would all be linked in one direction, from lowest
detail plan to highest level plan. The lowest of detailed plans would be
updated by timesheet. The remainder would be updated strictly by milestone
links.
Although I ask about three levels of plans, I believe I can successfully
keep the entire project (or program--collection of projects sharing the same
resources) to two levels.
I'd rather save time by asking before I spend too many hours setting it up
and having it blow up miserably.
Thanks!
project on MS Project Server 2003 if the master project consisted strictly of
milestones that are linked to other milestones from within other projects on
the same server.
I want the milestones in the other projects, as they are completed, to
update the milestones in the master project.
Or--am I making this too complicated? Should I make the master project
consist of the milestones from the other projects? In doing so would I be
causing issues if I published the Master Project on the server since the
master would consist strictly of milestones that do not have assigned
resources?
Would I be making issues worse if the milestones in the other projects were
themselves updated from "sub" projects (knowing that I would have to open and
update each project plan in the correct order, lower to higher, to be sure
the high-level plan is accurate?)
I have already referenced the "How to link tasks in a project across
projects." My projects would all be linked in one direction, from lowest
detail plan to highest level plan. The lowest of detailed plans would be
updated by timesheet. The remainder would be updated strictly by milestone
links.
Although I ask about three levels of plans, I believe I can successfully
keep the entire project (or program--collection of projects sharing the same
resources) to two levels.
I'd rather save time by asking before I spend too many hours setting it up
and having it blow up miserably.
Thanks!