PMO project gating

[Jeu]

Does Project Server or ms project 2007 support the concept of gating in a PMO
context?

e.g PMO wants the PM NOT to be able to update the 'project phase'.

Any way this can be achieved?

 

[Mike Glen]

Hi Jeu,

Try posting on the microsoft.public.project.server newsgroup (forum).
Please see FAQ Item: 24. Project Newsgroups. FAQs, companion products and
other useful Project information can be seen at this web address:
http://project.mvps.org/faqs.htm

Mike Glen
Project MVP

 

[Jack Dahlgren]

No. If a project manager has write access to the file they can modify any of
the project properties and activities within the file. The only things that
can be locked administratively would be baselines 0 -5 and the contents of
value lists (but not the selection of items from the list)

There are a few hacks which could work around this (separate files for each
phase perhaps?), but as a general rule, you have to manage this in some other
way than using tasks or project properties.

If you trust someone to manage a project (expending your organizations money
and people in the process) surely you can trust them with a project file? If
not, you have either not trained them or you have the wrong people.

-Jack Dahlgren

 

[Jeu]

Thanks for the reply Jack.

Well, we do trust our PMs, but the need for this requirement is more so that
proper PMO project portfolio reporting can be achieved. Just to be sure that
no phase changes go un-noticed by the PMO.

 

[Rob Schneider]

Instead of preventing the change (which is hard), write a little VBA
macro that checks for changes based on what the PMO would be checking
for. While at it, can include in that macro other QA checks.