J
jay
Desktop: MS Project Professional 2002 SP-1
Server: MS Project Server 2003 SP-1
In our enterprise environment, we have one rather large and highly visible
project with tasks and assignments managed by (4) different project managers.
The project has been executing for 5 weeks. The (4) managers frequently
experience contention waiting for the check-in of the project in order to
check-out to perform normal maintenance (e.g. changes, approve task updates,
etc.).
Up for consideration - split the enterprise project into (4) separate
projects by performing the following off-hours:
1. Save enterprise project off-line (.mpp)
2. Save (4) new .mpp's from original .mpp
3. Modify/tailor the (4) .mpp's specific to each area of responsibility
*since there is "risk" associated with copy & paste of full rows from
projects...delete the rows that are unneeded in each of the (4) projects
4. Project Server administrator archives and deletes original enterprise
project
5. Import (4) new .mpp's to server environment; managers publish to web to
re-populate Project Center and timesheets
Will this approach allow for the preservation of all the live project data
(e.g. baselines, actuals, etc.) so we don't miss a beat?
Typically, my preference is "Ready, aim, fire" as opposed to "Ready, fire,
aim" <g>
Thank you.
Server: MS Project Server 2003 SP-1
In our enterprise environment, we have one rather large and highly visible
project with tasks and assignments managed by (4) different project managers.
The project has been executing for 5 weeks. The (4) managers frequently
experience contention waiting for the check-in of the project in order to
check-out to perform normal maintenance (e.g. changes, approve task updates,
etc.).
Up for consideration - split the enterprise project into (4) separate
projects by performing the following off-hours:
1. Save enterprise project off-line (.mpp)
2. Save (4) new .mpp's from original .mpp
3. Modify/tailor the (4) .mpp's specific to each area of responsibility
*since there is "risk" associated with copy & paste of full rows from
projects...delete the rows that are unneeded in each of the (4) projects
4. Project Server administrator archives and deletes original enterprise
project
5. Import (4) new .mpp's to server environment; managers publish to web to
re-populate Project Center and timesheets
Will this approach allow for the preservation of all the live project data
(e.g. baselines, actuals, etc.) so we don't miss a beat?
Typically, my preference is "Ready, aim, fire" as opposed to "Ready, fire,
aim" <g>
Thank you.