Planned % Complete - MS Project

Submitted by Kayode Oni on
Microsoft Project

Member for

18 years 6 months
Member for 18 years 6 months
Submitted by Kayode Oni on Sun, 2009-08-02 09:31
Permalink

I accept, not enough detail in the example.

All baseline Dates.

Task 1 Milestone - Friday 31/07/09

Task 2 (FS) Task 1 - 5 Days - Monday 03/08/09 to Fri 07/08/09

Task 3 (FS) Task 2 - 10 Days - Monday 10/08/09 to Fri 21/08/09.

Overall duration is 16days (including milestone start date.)

Current status date is Fri 31.07.09 - End of play.



With Stats above, overall planned % complete (Baseline) as at 31.07.09 will be calculated as 33%, simple average.

Using the same stats as actual start & finish dates, automatically calculated by MSP, overall % complete will be 0% as at 31/07/09, simply because task 1 is a milestone - weighted average.

Hope my question is slightly clearer.




Member for

19 years 11 months
Member for 19 years 11 months
Submitted by Trevor Rabey on Sat, 2009-08-01 22:33
Permalink

Not the case?

If you say that the Summary % Complete in your example is not supposed to be 33%, what do you think it should be?



There is not enough information in your example.

What is the baseline start, finish and overall duration of the summary (due to the tasks predecessors, lag, dates etc)?

What is the baseline start, finish and overall duration of the tasks?

What is the current start, finish and overall duration of the summary (due to the tasks predecessors, lag, dates etc)?

What is the current start, finish and overall duration of the tasks?

Where is the status date?

Member for

18 years 6 months
Member for 18 years 6 months
Submitted by Kayode Oni on Sat, 2009-08-01 09:07
Permalink

Hi Trevor, thanks for the response.



May be I haven’t posed the question properly. The formula works well. Absolutely nothing wrong it. The issue I was referring to in my original post arises when attempting to get an overall Planned % complete for a project.

Using the average option for summary tasks, MSP takes an average of all planned %s. Sometimes, this doesnt give a true reflection. Weighted average(Function of duration etc) is required.

Example - Summary task with 3 subtasks

Task 1 - Milestone - 100%(Planned % Complete)

Task 2 - 5 days - 0% (planned % complete)

Task 3 - 10 days - 0% (planned % complete)

MSP will calculate Overall planned % complete as 33% -clearly not the case.

I guess solution the use of a weighted average column, just like MSP calculates normal roll up summaries. How?????

Member for

19 years 11 months
Member for 19 years 11 months
Submitted by Trevor Rabey on Sat, 2009-08-01 06:34
Permalink

I don’t agree. You say that the Summary calculation is not correct with Use Formula, but you don’t say why.

But of course it is correct because it has a Baseline1 Start and the calculation is just the ratio of the duration from the Baseline1 Start to the status date divided by the total Baseline1 Duration.



There are so many things that can go wrong with your formula that it is not worth doing unless you are prepared to account for other variables. For example, you use the Standard Calendar for all of the ProjDateDiffs, but the Tasks and Summaries might all use different calendars.



This is a lot of trouble to go to just to attempt to replicate something which is already built into the functionality of MSP.