D
Daniel Billingsley
I have created a master project consisting of two imported projects all
linked to a shared resource pool. MS Project leveled the resource across
both projects such that there is somewhat random work going on from both of
them across the next few months. The "random" way it prioritized, project2
ends up completed in a couple weeks and project1 is completed in a month or
so.
That's fine for a first try and all else being equal, but now the decision
has been made that the first project has to have more priority so it meets
its deadline. What I really want to tell Project is that I want to complete
the projects more or less in order. I say "more or less" because I may jump
in and work on a task on project2 next week when it fits in, but the key is
I never want MS Project to level such that any project2 tasks gets scheduled
before ones from project1
I've tried using the Priority, but it really has zero effect.
I've tried putting a start-finish constraint between the two projects, but
it doesn't like that because some work from project2 is already done and it
would end up being before project2's start date.
This seems like such a basic way master projects would be used that I must
be missing something. I ultimately would like to have the next year's worth
of projects in there and be able to order them in terms of leveling
priority.
linked to a shared resource pool. MS Project leveled the resource across
both projects such that there is somewhat random work going on from both of
them across the next few months. The "random" way it prioritized, project2
ends up completed in a couple weeks and project1 is completed in a month or
so.
That's fine for a first try and all else being equal, but now the decision
has been made that the first project has to have more priority so it meets
its deadline. What I really want to tell Project is that I want to complete
the projects more or less in order. I say "more or less" because I may jump
in and work on a task on project2 next week when it fits in, but the key is
I never want MS Project to level such that any project2 tasks gets scheduled
before ones from project1
I've tried using the Priority, but it really has zero effect.
I've tried putting a start-finish constraint between the two projects, but
it doesn't like that because some work from project2 is already done and it
would end up being before project2's start date.
This seems like such a basic way master projects would be used that I must
be missing something. I ultimately would like to have the next year's worth
of projects in there and be able to order them in terms of leveling
priority.