Practical use of Update Tasks process and %age complete - a PMO perspective?

[Roger]

Guys hi,
In terms of using a baseline and gaining information on project
variances in the real world, what have you experienced with PM's
updating or not updating their project tasks %age complete?

In your work place, is there an edict stipulated by management that is
well known by all PM's that is a non-negotiable requirement to update
their projects every Friday before COB?

Or

Is this an adhoc process, done when and if the PM has time. Is this
seen generally as an Admin overhead in project management, the first
thing to fall off the bench when 'times get tough'....?

I'm curious as to the setting up of best practices and standards
surrounding the use of baselining in general.

Regards
Roger

 

[Jim Aksel]

Ideally, your PM will be a guru in MS Project.... then the updates go smoothly.
Our company provides PM Services, largely to the big aerospace companies.
In every case, EV updates are due weekly at a certain time.

Control Account Managers are personally accountable to provide %Complete,
Remaining Work, Remaining Duration (Finish Date) updates every week By COB
Wednesday to support a network review on Friday morning. The days vary by
company but are very very firm.

Generally, we hold the Control Account Manager (usually a direct report to
the PM) accountable for the updates. Rarely do we let a CAM make the update
directly. They are usually distributed a PDF file, or Excel file with
appropriate information. We have Macros we run that flag specific tasks for
update and progress.

Taking the latter approach (Admin/Overhead function) clearly dismisses the
entire purpose of the schedule. The schedule is a forward planning tool ...
not wallpaper to document history. It needs to be a living document showing
the consequences of progress (or lack of progress) on the program. Such a
responsibilty is absolutely in the hands of Control Account Managers and PMO
personnel who are quite skilled at working the scheduling/Earned Value tools
(regardless of vendor).

Think about the importance of "baseline".... it is what you agree to "be
beat up by" from the program sponsors and funding organizations. You don't
want to let that fall by the wayside ... the PM will be blind sided and hung
out to dry with the laundry.

If you need additional information, click on my name and browse the links
there.
--
If this post was helpful, please consider rating it.

Jim Aksel, PMP

It''s software; it''s not allowed to win.

Visit http://project.mvps.org/ for FAQs and more information
about Microsoft Project