Best Practice

[Matium]

Hi all,

I have a project manager assigned to the highest level summary task for
my project, as he will be needed until the project finish. Is this good
pratice or what is the best way to monitor how his work will increase
if there is delays and the project gets extended?

 

[John]

Hi all,

I have a project manager assigned to the highest level summary task for
my project, as he will be needed until the project finish. Is this good
pratice or what is the best way to monitor how his work will increase
if there is delays and the project gets extended?

Matium,
Assigning resources to a summary line at any level is generally
considered bad practice. It can cause confusing results and in some
cases double booking. It could also interfere with the earned value
metrics.

A better approach is to set up a separate file for program management
tasks. When you consider it there is generally more than just the
program manager. There are also support personnel - business people,
contracts, data management, etc.

If an separate program management file is not appropriate, I suggest a
separate task be set up, perhaps directly under the top summary line. If
appropriate, this task can be a hammock task (see FAQ 19 - Hammock tasks
on our MVP website at: http://www.mvps.org/project/faqs.htm).

Hope this helps.
John
Project MVP

 

[Steve House [Project MVP]]

Create a hammock task that is whose duraton is driven by the project start
and end dates for the managment task(s) an assign the PM to it as tjhe
resource.