tracking a project

Hi Darren



We now find ourselves debating Faisal’s problem when he hasn’t a clue what to do about it even after all the advice.



I will now follow you to the nearest exit route on this thread.



Best regards



Mike Testro.

Mike,



Perhaps I’m labouring under a misapprehension, I thought the impenetrable predicament Faisal has found himself in was more to do with erroneous duration variance, as opposed to seeking advice on constructing a schedule based on sound precedence networks.



If such is the case I’ll extricate myself from this thread, as it’s a theoretical lesson he needs not hands-on issue resolution.



Regards,



Darren

Hi Darren



The situation friend faisal is facing is when a 20 day delay at the begining of the job generates a .25 delay at the end.



No one has yet advised him od what to do to get the programme moving dynamically.



Best regards



Mike Testro

Mike



All valid points, however, to specifically calculate duration variance MS Project doesn’t need to use closed network or critical path as a reference, just a baseline. Now here’s one to get your wind up ;o)



Faisal



Are you using leads or lags?

Hi Faisal



Please go back to my thread #4.



Are you using up excessive float?



Do you have a clear critical path?



Are all the links in place?



Best regards



Mike Testro

For a start I’d download Service Pack 2 just to be sure and then see if the problem persists.

Do you split in-progress tasks?

Have you download SP2 for MS Project 2k7?

Faisal,



Are you using elapsed durations? (e-days)

Is your calculation mode set to manual or automatic?



Regards,



Darren

Hi Faisal,

Are ALL of the task durations whole days and not decimals?
Are ALL of the baseline task durations whole days and not decimals?
Are ALL of the tasks using the same task calendar?
Are ALL of the resource base calendars the same as the task calendar?
Do the default options on the calendar tab match the task and resource base calendars?
If you change the date format to show ddd dd/mm/yy hh:mm, are ALL of the start/finish times the same as the default options on the calendar tab?
And finally, are ALL of the baseline start/finish times the same as the default options on the calendar tab?

You calculate the Duration Variance from Duration - Baseline Duration, so you need to check all possible associations between the two.

Regards,

Darren

Faisal,

How do you know that there are no date constraints?

Can you see the Indicators column?

Is there a "calendar" icon in it?



Do you have a complete, closed network, with every Task having at least one FS predecessor and at least one FS successor?



If you have a complete, valid CPM network, then if your tasks that have started started late, or took longer than estimated, or finished later than their early finish, and if they are on the critical path, then when you update them the project finish date will move right. Not happening?

Hi Faisal



Are you using up float?



Best regards



Mike Testro

Hi Faisal



It seems as if you have some constraint flags that are distorting the critical path.



Remove them all and re-schedule.



Best regards



Mike Testro