D
Darrell
Can anyone provide some input on the best method for handling the following
situation?
I have project managers with project plans containing thousands of lines,
most of which are completed tasks that in some cases can be several years
old. When I ask why, I am told they need to keep all of this information
together in one file because of the contracts, etc. (whatever). It makes
opening, saving, publishing, etc. take forever and some will not even open in
the Project Center views. These are software schedules and each new upgrade,
change order or release can be managed as a separate module so I want them to
be a separate schedule versus adding to the existing schedule.
My question is this. What would be the best method to be able to manage each
release as a separate project schedule and still maintain all of the same
information in a master schedule?
All input greatly appreciated, instructions or links to a documented process
would be the cat’s meow!
Thx
Darrell
situation?
I have project managers with project plans containing thousands of lines,
most of which are completed tasks that in some cases can be several years
old. When I ask why, I am told they need to keep all of this information
together in one file because of the contracts, etc. (whatever). It makes
opening, saving, publishing, etc. take forever and some will not even open in
the Project Center views. These are software schedules and each new upgrade,
change order or release can be managed as a separate module so I want them to
be a separate schedule versus adding to the existing schedule.
My question is this. What would be the best method to be able to manage each
release as a separate project schedule and still maintain all of the same
information in a master schedule?
All input greatly appreciated, instructions or links to a documented process
would be the cat’s meow!
Thx
Darrell