|
07-24-2015, 05:51 AM
|
|
Expert
|
|
Join Date: Dec 2011
Location: New England
Posts: 1,693
|
|
Case FOR Separate files:- If the projects need to be reported individually, that does argue for separate project files that can be combined as needed in a master project.
- The advantage of separate projects is if they have differing PMs each can be updating his/her project file while another PM is updating their file.
- If using individual projects and master - you only need to have the master file hold the "active" projects. If a project is not yet begun or has finished, the files do not need to be in the master.
Case against separate files:- If you are using the same resources - you need to create a resource pool to keep track of possible resource overallocations. Resource pools need to be treated carefully and all user touching the project files attached to the pool need to have a very solid understanding of how MS Project works.
- Care needs to be taken to make sure each individual project file is never moved or copied as this creates havoc with the master. Suggest to never save the master but to re-create as needed.
Case for putting everything in one file:- Easy to see everything going on.
- All updates are contained within one file.
- Can use a spare text field for identifiers for what product is being produced.
- No concerns about resource pools - all the tasks and all resources are contained in one project file.
Case against:- 6000 lines is a bit much for the PM to keep track of.
- Need to answer the question of what will you do with projects that are complete? Do you delete their tasks to keep the project file in control?
I hope this helps.
|