Best Practice for accepting Task Updates

[Christina]

I have read several sources that suggest PMs only accept updates for one
project at a time. I have also been told that the project in question should
not be opened at the time the updates are approved.

I am working to create standards and guidelines for PMs in our organization
based on these Best Practices but need to be able to articulate the reasons
why. I think I can understand the potential problems of accepting task
updates which the project open. But I don't know the reason for only
accepting updates for one project at a time.

Can someone explain this to me?

Thanks!
Christina

 

[Jonathan Sofer [MVP]]

Is this for MSPS 2003?

The reason for accepting updates to one project at a time I think has to do
more with the ability for the PM to work through the updates in a clear
manner and not get overloaded with the number of changes that are coming
through.

 

[Christina]

I'm sorry. Yes, this is for a 2003 environment.

So, are your thoughts that there wouldn't be any technical ramifications of
accepting updates for more than one project at a time?

 

[Marc Soester [MVP]]

HI Christina,

technically you are able to update more then one project in Project Server
2003 and somethimes this may be ok to do. From a technical point of view I
can see that performance will be an issue when you update lets say 10
projects at the same time. The reason for this is because project server
loads now 10 projects in the MS Project and that can take a while depending
on the size of the project schedule.

From a process point of view, it may be easier to check one project at a
time for the PM's. It alows the PM not to get confused. It obiously also
depends if it is only one update from ine Resource or from 20 REsources.

I hope this helps
--
Marc Soester [MVP]
National Manager: EPM
http://marcsoester.blogspot.com

 

[Christina]

Hi Marc-

Yes, that does help.

thank you very much!

Christina