Update sub-project>indicating change in masterplan>review then acc

[Harry Seymour]

Hi,

I’m working on a programme plan managing several Projects (in Vista). I
need a Master programme plan has the projects inserted. I also want to
create dependencies between the projects.

However, when one of the projects update its timeline I need to ensure that
it does not immediately impact other project timelines (in the master or
other project plans). What I do want to happen is for the Master to show
that a change has been made, what that change is, but not immediately accept
it and adjust all other project plans.

This will allow the manager of the Master plan to review and understand
changes before they’re accepted, and also discuss and communicate changes to
the project plans.

Do you know how I can do this? It could be as simple as flashing a task red
(in the Master) when it has been changed in a Project plan then a simple
mechanism to ‘accept’ the change which would then feed the change into the
other plans.

thanks
Harry

 

[John]

Hi,

I’m working on a programme plan managing several Projects (in Vista). I
need a Master programme plan has the projects inserted. I also want to
create dependencies between the projects.

However, when one of the projects update its timeline I need to ensure that
it does not immediately impact other project timelines (in the master or
other project plans). What I do want to happen is for the Master to show
that a change has been made, what that change is, but not immediately accept
it and adjust all other project plans.

This will allow the manager of the Master plan to review and understand
changes before they’re accepted, and also discuss and communicate changes to
the project plans.

Do you know how I can do this? It could be as simple as flashing a task red
(in the Master) when it has been changed in a Project plan then a simple
mechanism to ‘accept’ the change which would then feed the change into the
other plans.

thanks
Harry

Harry,
I assume you know how to create the dynamic master (i.e.
Insert/Project). I also assume you know how to set up external links
between tasks in the subprojects.

As far as "holding" the changes of one subproject from changing the
master or other subprojects, the only way is to not save. In other
words, make the desired changes to the subproject and then have the
manager review the impact immediately. Once the changes are reviewed and
accepted, then the master and other subprojects can be saved.

John
Project MVP

 

[Harry Seymour]

John,

Thanks for your response.

So there's no way in the Master View that it highlights changes made in the
sub-projects before they're made. It seems that you're saying the review
would have to be made on the subproject before it is submitted into the
Master.

This is a shame, it seems a great piece of functionality would be to
highlight where a sub-project has changed, then accept or decline this change
in the master which would then impact all plans. I'm amazed there is no way
to do this as would help manage large programmes.

Harry

 

[John]

John,

Thanks for your response.

So there's no way in the Master View that it highlights changes made in the
sub-projects before they're made. It seems that you're saying the review
would have to be made on the subproject before it is submitted into the
Master.

This is a shame, it seems a great piece of functionality would be to
highlight where a sub-project has changed, then accept or decline this change
in the master which would then impact all plans. I'm amazed there is no way
to do this as would help manage large programmes.

Harry

Harry,
You're welcome. I neglected to mention that Project 2007 does have
change highlighting - previous versions do not. And, change highlighting
does work at the master file level.

So the bottom line is that the functionality you desire has been
included in the latest version of Project.

Hope this helps.
John
Project MVP