% Worked <> % Complete

[EarlePearce]

If we were getting paid by the number of bricks set, it's conceivable that
the first 50% of the bricks might be set in 30% of the time for all bricks.
So how do we know when we hit 50%?

We don't do bricks but our projects usually have a large disconnect between
hours and % done. So we added columns for the PM to enter "% Done".
However, not all tasks contribute equally to the summary task, so we also
added a column for the % value of the task to summary and one to show the net
value of % Done * % Value.

Well, not all summary tasks are equal to the next level, so.... now I have 5
columns which only deal with rollup for the bottom 2 levels. Currently this
project has 4 levels but may gain more once we get into it.

I want to get % 'really' done at each level, including the project itself.
I am accomplished writing VBA for Access and started writing for Project but
got tangled and question if this is the right approach. Should I be looking
at the row level or should I approach it as a function rolling up the entire
project when called?

I know this is your chance to sell me a book and I'll buy, but which one is
geared to this level of complexity? Of course I'll accept all the help you
give.

Earle

 

[Gilgamesh]

If we were getting paid by the number of bricks set, it's conceivable that
the first 50% of the bricks might be set in 30% of the time for all
bricks.
So how do we know when we hit 50%?

We don't do bricks but our projects usually have a large disconnect
between
hours and % done. So we added columns for the PM to enter "% Done".
However, not all tasks contribute equally to the summary task, so we also
added a column for the % value of the task to summary and one to show the
net
value of % Done * % Value.

Well, not all summary tasks are equal to the next level, so.... now I have
5
columns which only deal with rollup for the bottom 2 levels. Currently
this
project has 4 levels but may gain more once we get into it.

I want to get % 'really' done at each level, including the project itself.
I am accomplished writing VBA for Access and started writing for Project
but
got tangled and question if this is the right approach. Should I be
looking
at the row level or should I approach it as a function rolling up the
entire
project when called?

I know this is your chance to sell me a book and I'll buy, but which one
is
geared to this level of complexity? Of course I'll accept all the help
you
give.

Are you perhapes referring to the standard MS Project column %Work

 

[Rod Gill]

Why not just back load a task's assignment with work. So the first half of
the Task has 30% of the work and the last part of the Task 70%? Then update
progress based on % work complete.

You can either choose a profile for an assignment, or manually adjust the
work in a usage View.

--

Rod Gill
Project MVP

Project VBA Book, for details visit:
http://www.projectvbabook.com

NEW!! Web based VBA training course delivered by me. For details visit:
http://projectservertraining.com/learning/index.aspx

 

[Jan De Messemaeker]

Hi,

Isn't this what Physical%complete is for?
And are the sums you want at summary level Earned Value?

 

[EarlePearce]

Of course you are right in using work remaining & I'm now re-reading my SBS
book. In a couple days I'll have that worked out.

The bigger problem is calcing the weighted values of each task to it's
parent. Some tasks are simply do some paperwork or hammock time. They may
be 1 of 4 tasks but do not contribute 25% to the parent completion.

I'm ducking as I say this, but we want to see percent done in "billable
terms". If we plot billing milestones we must have billable hours and
specific tasks completed (often listed in contacts) to have a good invoice.
Some tasks are not billable but necessary. So, when my method says a phase
is 50% complete, I can bill it as 50% complete.

I thought I may be able to write code to walk the task table and calc within
each parent group but I got tangled trying to keep children associated with
parents above the bottom levels. Maybe the outline number or custom WBS, or
perhaps there is an association table I haven't found yet that I can access
in code. But what really works and how?

Earle

 

[Rod Gill]

In VBA use Activecell.Task.OutlineParent.Name to read the name of the
summary task.

--

Rod Gill
Project MVP

Project VBA Book, for details visit:
http://www.projectvbabook.com

NEW!! Web based VBA training course delivered by me. For details visit:
http://projectservertraining.com/learning/index.aspx

 

[Jim Aksel]

I agree Jan, Physival%Complete... oddly enough, the help systems uses the
example of laying bricks when discussing Physicval%Complete. It appears all
that is needed here is a properly costed resource, and a resource loaded
schedule. After that, it's all Earned Value. insert the BCWP column and
it's done.
--
If this post was helpful, please consider rating it.

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

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

 

[Steve House]

FYI - the way Project calculates the % Complete of a summary task (as best I
can determine) is that it divides the sum of the subtask's actual durations
by the sum of their total durations and multiplies the result by 100 to
convert to a percentage. This way the effective % Complete of the summary
is the same regardless of whether the subtasks are sequential, in parallel,
something in between, or have lead times or lag times. To calculate the
summary Actual Duration and Completed Through date, a couple more steps are
required. (A normal activity's Completed Through is just the Start date
plus Actual Duration but that doesn't work for summaries.) It takes the
Summary % Complete and multiplies it by the Summary Duration to get the
Summary Actual Duration. It subtracts the Summary Actual from the Summary
Duration to get the Summary Remaining Duration. It then subtracts the
Summary Remaining Duration from the Summary Finish Date to come up with the
Summary Completed Through date. This way gaps due to lag times, leveling
delays, etc that can make the summary duration longer than the sum of the
subtask durations are properly taken into account.

HTH