Problem with using *.mpp files on shared network drive with inter-project links

[anovak]

Until we are up and running in a few months with a new implementation
of Project Server, we decided to use flat files for now for a major
initiative which contains sub-plans and inter-project task
dependencies. The sub-plans were all split into separate *.mpp files
so that they can edited simultaneously and the team leads wouldn't
walk on each other.

Case in point...

One of the sub-plans is for the HR area and the Team Lead has that
file open although he is just reading it.

Meanwhile the Program Manager opens the Master *.mpp and proceeds to
change some links between one of the sub-plans and the HR plan (which
he doesn't know is already opened by someone else).

When he attempts to save the Master, he is given a warning at THAT
time that the HR sub-plan is already open and is given an opportunity
to "Save As" on that sub-plan.

So, he saves as "HR V1" because a great deal of editing had been done
on the fly and he didn't want to lose the changes.

NOW, all the links are pointing to HR V1 from the other sub-plans
instead of to the original HR mpp file. The links were removed from
the original file.

What is the "best practice" smooth over the road bumps here until we
get Project Server 2007 going? One would hope that when you open the
Master, you would be given a warning at that moment that one of the
sub-plans is opened by another user. If that had been the case, the
Program Manager would have waited until that sub-plan was closed.

Thanks,
Andy Novak
University of North Texas

 

[Rod Gill]

One safe way is not to link tasks, but to have extra milestones representing
agreed delivery dates from other projects. This requires manual
communication and editing but it's safe (no chance of corruption which
inappropriate handling of linked files can cause) encourages more
communication and is simple.

--

Rod Gill
Project MVP

NEW!! Project VBA Book, for details visit: http://www.projectvbabook.com

 

[anovak]

I assume that if your'e running Project Server, what you would want to
do is:

1. House all tasks within one physical plan

2. Make the Program Manager the "Plan Owner"

3. Make each Team Lead / Project Lead the "Project Manager" for each
section they are responsible for

4. Use PWA-based progress reporting and each lead approves the
progress on each of their sections.

Would someone please affirm this?

Thanks,
Andy