I would not type in dates (except actuals) and produce date constraints such as FNET because they screw up everything and also are not appropriate or necessary in this case.
Maya, I think that you have pushed the entire 15 days out to the right of the status date because you have given the Task an Actual Start but have not logged the duration used as Actual Duration, and then "re-scheduled work" with the 3rd button on the Tracking Toolbar.
Suppose a 10 day Task started as planned 5 days before the Status Date but was worked on only for 2 days and then paused. you would still have 3 days of unused duration to the left of the status date which has to be moved to the right of the status date, ie it can only occur in the future. So type in the Actual Start Date (a fact), type in the Actual Duration (a fact), move the unused Duration to the right of the status date (3rd button on the Tracking Toolbar), re-estimate the Remaining Duration (or leave it alone, which anyway amounts to a decision estimate it at whatever it is).
Member for
22 years 9 months
Member for22 years9 months
Submitted by Alexandre Faul… on Sat, 2007-09-08 03:58
as MS Project does not know what Expected Finish is, I would enter the date 09/04/2007 in the scheduled finish field; MS Project understands this as "Finish No Earlier Than" (see Task Infos, Advanced, Constraint Type)
this way, the Tracking dialog box displays an actual duration going from the actual date to the status date, and a remaining duration from the status date to the expected finish date
On the Activity Tracking dialog box it says that it has 13 days complete and an RD of only 2, but the program has scheduled all 15 days beyond the Project Status Date which is 09/02/07. What am I doing wrong.
Member for
19 years 11 months
Member for19 years11 months
Submitted by Trevor Rabey on Thu, 2007-09-06 23:48
The Task Type being Fixed Units is not part of this issue.
You dont really describe how you are going about it that is not producing the desired result.
When Tracking, it is important to set things up so you can see what you are doing, and develop a simple, consistent, repeatable procedure and stick to it.
Here is a procedure that I find useful:
Set a Baseline
Set a Status Date
Show the Tracking Gantt View
Show the Tracking Table
Show the Tracking Toolbar
Format the Gridlines to show the Status Date as a vertical red line
Then... select the Task, type in the Actual Start Date, use the Update As Scheduled button (2nd from left)on the Tracking Toolbar, then type in the new estimate of the Remaining Duration, ie the RD that makes the expected Finish Date 9/24/2007 (although in this case RD should not change).
The sequence is important.
The Remaining Duration re-estimate, if required, is v important.
If the picture that you paint is not consistent with and/or contradicts the facts, it is wrong.
Member for
19 years 11 monthsRE: Problem with dates...
I would not type in dates (except actuals) and produce date constraints such as FNET because they screw up everything and also are not appropriate or necessary in this case.
Maya, I think that you have pushed the entire 15 days out to the right of the status date because you have given the Task an Actual Start but have not logged the duration used as Actual Duration, and then "re-scheduled work" with the 3rd button on the Tracking Toolbar.
Suppose a 10 day Task started as planned 5 days before the Status Date but was worked on only for 2 days and then paused. you would still have 3 days of unused duration to the left of the status date which has to be moved to the right of the status date, ie it can only occur in the future. So type in the Actual Start Date (a fact), type in the Actual Duration (a fact), move the unused Duration to the right of the status date (3rd button on the Tracking Toolbar), re-estimate the Remaining Duration (or leave it alone, which anyway amounts to a decision estimate it at whatever it is).
Member for
22 years 9 monthsRE: Problem with dates...
Maya,
as MS Project does not know what Expected Finish is, I would enter the date 09/04/2007 in the scheduled finish field; MS Project understands this as "Finish No Earlier Than" (see Task Infos, Advanced, Constraint Type)
this way, the Tracking dialog box displays an actual duration going from the actual date to the status date, and a remaining duration from the status date to the expected finish date
hope this helps,
Alexandre
Member for
18 years 5 monthsRE: Problem with dates...
Thanks Trevor,
I am still having this issue:
On the Activity Tracking dialog box it says that it has 13 days complete and an RD of only 2, but the program has scheduled all 15 days beyond the Project Status Date which is 09/02/07. What am I doing wrong.
Member for
19 years 11 monthsRE: Problem with dates...
The Task Type being Fixed Units is not part of this issue.
You dont really describe how you are going about it that is not producing the desired result.
When Tracking, it is important to set things up so you can see what you are doing, and develop a simple, consistent, repeatable procedure and stick to it.
Here is a procedure that I find useful:
Set a Baseline
Set a Status Date
Show the Tracking Gantt View
Show the Tracking Table
Show the Tracking Toolbar
Format the Gridlines to show the Status Date as a vertical red line
Then... select the Task, type in the Actual Start Date, use the Update As Scheduled button (2nd from left)on the Tracking Toolbar, then type in the new estimate of the Remaining Duration, ie the RD that makes the expected Finish Date 9/24/2007 (although in this case RD should not change).
The sequence is important.
The Remaining Duration re-estimate, if required, is v important.
If the picture that you paint is not consistent with and/or contradicts the facts, it is wrong.