Robert said:
We do have a fairly intensive process for getting status on tasks by various
groups on a bi-weekly basis. As the PMO, we are responsible for maintaining
the master schedule and due to the various levels of MS Project expertise, we
have one administrator keeping the schedule up to date. We don't have the
option at this time to subdivide the project schedule.
Do you know of any other options, short of splitting it into subprojects,
that would help with the size?
Robert,
It sounds like you have some serious file bloat. Go to our MVP website
at,
http://www.mvps.org/project/faqs.htm, and take a look at FAQ 43 -
handling Project file corruption and/or bloat.
Project files can balloon in size if not carefully maintained and saved.
Constantly editing and using the "Save" button will just keep adding
bulk to the file. A much better approach is to always use "Save As" back
to the same file name.
Depending on how much history you want/need to drag along, you might
want to consider doing a periodic (e.g. monthly, quarterly) save to an
archive and then collapsing the remaining file. When I say collapse I
don't mean simply collapsing the outline, I mean re-configuring the
completed tasks into equivalent task data. For example, take a group of
tasks under one or more summary lines and replace them with a single
task that is equivalent in work, time, cost and whatever other data is
important in your situation. I used this approach years ago, (with the
help of a macro), to periodically reduce the size of our files, and
those files were under formal change and earned value control. We had
the historical backup if needed and it make working with large files a
whole lot easier.
Hope this helps.
John
Project MVP