% complete at Parent WBS showing 11% even project completed more than 100%

Rushikesh,

1. In MSP, with some exceptions concerning milestones, the %Complete for a summary task is computed as the summation of the subtask Actual Durations divided by the summation of the subtask Durations.  Baseline Duration is irrelevant.
2. The 11% Complete value for the project implies that the current schedule (including Durations of the completed subtasks) is substantially different from the Baseline.  Had the first three subtasks been completed exactly as planned (i.e. their Actual Durations matched their Baseline Durations) with no other schedule changes, then the project %Complete would be about 26%.  Absent other schedule changes, the 11% value is consistent with the Actual Durations for the completed works being only about 37% of the Baseline Durations.
3. This example demonstrates that %Complete in MSP – a Duration-only metric – is not at all useful for progress valuation in cost-loaded schedules.  MSP provides separate Earned Value functionality for that purpose.

Good luck, tom

Hi,

I have a query with regards to an issue I have experienced in Microsoft Projects.

Below extract contains an activity:   “ Install P02-581-CNV-001 Crusher Discharge Chutes”, Activity ID 2447.  This activity has an Actual Start of 1 April 2019 and progressed to 30%.  What are the key influences for the forecast finish to reflect an October 2019 date whilst I know for a fact that the activity will be completed before end of June?  The schedule is resourced and therefore progress recorded in % Work Complete.

Thanks,

Johan

Johan,

You asked, "What are the key influences for the forecast finish to reflect an October 2019 date whilst I know for a fact that the activity will be completed before end of June?"

Possible influences on the forecast delay of remaining work for task 2447 are:

1. This task has started out of sequence (i.e. its predecessor was not complete) AND "Split in-progress tasks" Schedule option is checked, AND the incomplete predecessor is delayed until October.  As for all out-of-sequence progress, fix the relationship that you know to be wrong.

2. MFO or FNET constraint in October is applied to the task, OR ALAP constraint is applied to the task.

3. The Resume date of the task has been delayed by one of the following:

     - manual entry or other incorrect update procedure;

     - resource leveling.

4. Resource assignments have been delayed or otherwise modified by user entry or by the resource leveler.

Good luck, tom