Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Tracking using % complete

6 replies [Last post]
Rohit K
User offline. Last seen 4 years 6 weeks ago. Offline
Joined: 2 May 2008
Posts: 73

874
microsoft_project_-_baseline.jpg
Hi all,

Can a schedule from 15.02.11 to 14.08.12, duration of 547 days tracked as on 15.01.12, have a finish variance of 1389 days?

The above instance is for a schedule of my project. The schedule is tracked based on % complete. I am manually entering the % complete as on the status date. For me to report % complete is the percentage of quantity of that task being completed as on the status date.

Earlier the same schedule tracked a fortnight ago had a finish variance of 153 days as on 31.12.11.

Also on saving as a Baseline and then inputting the values why does the start / finish varies from baseline start / finish dates?

Rohit

Replies

Donald Harrold
User offline. Last seen 11 years 48 weeks ago. Offline
Joined: 30 Mar 2011
Posts: 38
Rohit, My preferred way to use MS Project is to create all activities as fixed work type and then update the schedule by entering an actual start date and entering the completed work using the % work complete field. The work to go and the finish date can then be forecast by editing the Remaining Duration and Remaining Work fields. Doing this I have found that MS Project gives the most stable and predictable results. D
Anning Sofi
User offline. Last seen 6 years 2 weeks ago. Offline
Joined: 22 Jan 2012
Posts: 89
Groups: None

To resolve your issue on the 1389 days, try this check:

1) Filter all 100% complete activities

2) Check if your 100% complete activities have actual finish dates.

3) Update the finish dates for the 100% complete activities which has no actual finish dates.

4) rerun F9

5) variance should be correct now

DONE

Rohit K
User offline. Last seen 4 years 6 weeks ago. Offline
Joined: 2 May 2008
Posts: 73

Trevor,

Thanks for your explanation.

I know that % complete is for the duration and not for the progress of work. But I am unsuccessful in trying to make my clients understand the logic and hence forced to follow the above system of reporting. Earlier in my other projects I was using the % physical complete, along with the actaul start / finish / remaining durations and then updating the schedule on the status date.

Rohit

Hlamalani Baloyi
User offline. Last seen 12 years 6 weeks ago. Offline
Joined: 20 Jan 2012
Posts: 18
Groups: None

You cannot just enter %complete, you need to track the actual events, "Actual Start Time, Actual finish Time" then you will get correct information, You baseline is normally different from your ctual information and hence you can forecast you finish date correctly, otherwise if you want your actual information to be the same as the baseline it then becomes useless, it means you are not planning but you are only data capturing.

Trevor Rabey
User offline. Last seen 1 year 38 weeks ago. Offline
Joined: 29 Nov 2005
Posts: 530
Groups: None

"For me to report % complete is the percentage of quantity of that task being completed as on the status date."

This is incorrect. % Complete is actual duration/total duration. That's all it is. If you set out to lay 10000 bricks in 10 days and at the end of the 6th day you have only laid 3000 bricks, the % Complete is 60%, but the % Bricks is only 30%.

If you observe that the task is % Vricks is 30% and you type that into the % Complete field the it is wrong because first of all the number is about bricks but you have put it in the field that is about duration, and it is wrong because you have told MSP that there has been 3 days of actual duration when there has actually been 6. It starts wrong an gets worse wrong!

Also, you must also record the facts, which are the actual start and the actual duration. Then you must record the actual duration, which is some number up to but no more than 6. Then you must re-estimate the remaining duration (is 4 days enough?)

Hope this helps.
 

Trevor Rabey
User offline. Last seen 1 year 38 weeks ago. Offline
Joined: 29 Nov 2005
Posts: 530
Groups: None

"For me to report % complete is the percentage of quantity of that task being completed as on the status date."

This is incorrect. % Complete is actual duration/total duration. That's all it is. If you set out to lay 10000 bricks in 10 days and at the end of the 6th day you have only laid 3000 bricks, the % Complete is 60%, but the % Bricks is only 30%.

If you observe that the task is % Vricks is 30% and you type that into the % Complete field the it is wrong because first of all the number is about bricks but you have put it in the field that is about duration, and it is wrong because you have told MSP that there has been 3 days of actual duration when there has actually been 6. It starts wrong an gets worse wrong!

Also, you must also record the facts, which are the actual start and the actual duration. Then you must record the actual duration, which is some number up to but no more than 6. Then you must re-estimate the remaining duration (is 4 days enough?)

Hope this helps.