When updating it is useful to first get to the right View and Table so you can see whats happening, and then follow a consistent procedure every time, like:
Show Tracking Gantt
Show Tracking Table
Show Tracking Toolbar
Set Baseline
Set Status Date
Format the gridlines to show Status Date (a fat red vertical line).
Then type in Actual Start and Actual Finish Dates.
If the Task is not Finished, type in Actual Start Date, and Actual Duration, Then Remaining Duration.
The second and third buttons on the Tracking Toolbar are for:
1 ) when work has been done continuously from Actual Start to Status Date, update to the Status Date, then re-estimate Remaining Duration.
2) When work was discontinued after an initial Start, move the unused portion of the Duration (which is to the left of the Status Date Gridline) to the right of the Status Date, then re-estimate Remaining Duration.
Always review/re-estimate Remaining Duration, even if just to leave it as is.
Always use explicit Actual Start and Finish Dates.
Never type in % Complete (let MSP calculate it for you), except for maybe 0% and 100%.
This procedure is pretty reliable and can be extended for situations where Work (Hours) and/or Cost do not get automatically get updated along with Duration.
no wonder i find msp so unpredictable if we update the project. (as we normally would when using p3) msp is good for initial planning; quick and easy, but once u start to update/progress... all hell break loose!!! aaargh!
that explains why some company who uses msp, prefer to "update" by means of progress line update only... the zig-zag progress line at the status date over the "baseline" schedule.
Member for
20 years 7 months
Member for20 years7 months
Submitted by Niek Zonneveld on Thu, 2007-04-05 05:32
Be aware that MS Project was originally not designed to do this, and it uses some less elegant tricks to achieve that result.
It puts constraints on not-started activities in order to reschedule work after the status date. This will override any existing earlier constraint dates and create constraints on activities that never had one.
Furthermore, for in-progress activities it uses the resume dates to reschedule the remaining work, and in doing so, it overwrites the resume dates of any suspended activities that lay before the status date.
I suppose they could have put it in the Tools/Options/Calculation dialogue box together with the other switches related to the positioning of the remaining duration relative to the status date but then that would make the software user friendly!!
Member for
22 years 9 months
Member for22 years9 months
Submitted by Alexandre Faul… on Wed, 2007-04-04 03:46
Member for
19 years 11 monthsRE: Remaining Duration & the Status Line
I dont find MSP so "unpredictable".
When updating it is useful to first get to the right View and Table so you can see whats happening, and then follow a consistent procedure every time, like:
Show Tracking Gantt
Show Tracking Table
Show Tracking Toolbar
Set Baseline
Set Status Date
Format the gridlines to show Status Date (a fat red vertical line).
Then type in Actual Start and Actual Finish Dates.
If the Task is not Finished, type in Actual Start Date, and Actual Duration, Then Remaining Duration.
The second and third buttons on the Tracking Toolbar are for:
1 ) when work has been done continuously from Actual Start to Status Date, update to the Status Date, then re-estimate Remaining Duration.
2) When work was discontinued after an initial Start, move the unused portion of the Duration (which is to the left of the Status Date Gridline) to the right of the Status Date, then re-estimate Remaining Duration.
Always review/re-estimate Remaining Duration, even if just to leave it as is.
Always use explicit Actual Start and Finish Dates.
Never type in % Complete (let MSP calculate it for you), except for maybe 0% and 100%.
This procedure is pretty reliable and can be extended for situations where Work (Hours) and/or Cost do not get automatically get updated along with Duration.
Member for
19 yearsRE: Remaining Duration & the Status Line
thanks neik.
no wonder i find msp so unpredictable if we update the project. (as we normally would when using p3) msp is good for initial planning; quick and easy, but once u start to update/progress... all hell break loose!!! aaargh!
that explains why some company who uses msp, prefer to "update" by means of progress line update only... the zig-zag progress line at the status date over the "baseline" schedule.
Member for
20 years 7 monthsRE: Remaining Duration & the Status Line
Be aware that MS Project was originally not designed to do this, and it uses some less elegant tricks to achieve that result.
It puts constraints on not-started activities in order to reschedule work after the status date. This will override any existing earlier constraint dates and create constraints on activities that never had one.
Furthermore, for in-progress activities it uses the resume dates to reschedule the remaining work, and in doing so, it overwrites the resume dates of any suspended activities that lay before the status date.
Member for
22 years 6 monthsRE: Remaining Duration & the Status Line
Alexandre, Thanks for your comment.
I suppose they could have put it in the Tools/Options/Calculation dialogue box together with the other switches related to the positioning of the remaining duration relative to the status date but then that would make the software user friendly!!
Member for
22 years 9 monthsRE: Remaining Duration & the Status Line
Phil,
this functionality is rather new to MS Project; they missed clear space to put it in a dialog box, and they missed a self explanatory nam for it
Alexandre
Member for
22 years 6 monthsRE: Remaining Duration & the Status Line
Eugene, Thanks for your help, it now works!!
Dont know if MS could have hidden that switch any better. Long live Primavera!!!
Rgds, Phil
Member for
19 yearsRE: Remaining Duration & the Status Line
hv u execute the function to...
Schedule remaining work to start after status date?
it is found in Tools/Project Tracking...