L
L. Davis
Hello,
We are learning how to utilize the "status date" feature for tracking
updates to our milestone plan. The PMO team was previously making
manual weekly updates to these plans but we would prefer to start
having milestone owners log in and make updates through PWA. Ideally,
if someone marks a milestone 100% complete on, say, Friday, 4/10/09,
and the update is approved into the plan on Monday, 4/13/09, the
status date set to 4/10/09 would force the finish date to be 4/10/09
rather than 4/13/09. This is what we are trying to do for different
combinations of start and finish dates (i.e. current start/current
finish; current start/future finish; past start/current finish; future
start/future finish; past start/future finish; and past start/past
finish).
The 4 checkboxes are (Tools --> Options --> Calculation tab):
1 - Move end of completed parts after status date back to status date
1a - And move start of remaining parts back to status date
2 - Move start of remaining parts before status date forward to status
date
2a - And move end of completed parts forward to status date
In testing out the behavior of the task finish dates under the various
scenarios that these 4 checkboxes create, I have not been able to find
100% consistency with the status date results. I have found that no
combination of the past, current, and future start and finish dates
create results where if I mark all the milestones complete in PWA and
then incorporate the results using a start date set to a recent past
date (for example, 4/10/09), ALL the finish dates are updated to
4/10/09. In the scenario that almost passed, when all 4 boxes are
checked, one scenario still fails:
Past Start date/Current Finish date: The finish date at the resource
level is equal to the status date (4/10/09) but the task-level finish
date does NOT equal status date. The finish date at the task level is
updated to 4/17/09 (current date, not the status date).
This same scenario fails when more then one resource is assigned to it
and both mark the milestone 100% complete.
This is all very difficult to explain, but perhaps I just don't
understand the behavior of each well enough to determine how it is
generating the finish dates. Can you provide any insight into how
this would work best?
Thanks!
We are learning how to utilize the "status date" feature for tracking
updates to our milestone plan. The PMO team was previously making
manual weekly updates to these plans but we would prefer to start
having milestone owners log in and make updates through PWA. Ideally,
if someone marks a milestone 100% complete on, say, Friday, 4/10/09,
and the update is approved into the plan on Monday, 4/13/09, the
status date set to 4/10/09 would force the finish date to be 4/10/09
rather than 4/13/09. This is what we are trying to do for different
combinations of start and finish dates (i.e. current start/current
finish; current start/future finish; past start/current finish; future
start/future finish; past start/future finish; and past start/past
finish).
The 4 checkboxes are (Tools --> Options --> Calculation tab):
1 - Move end of completed parts after status date back to status date
1a - And move start of remaining parts back to status date
2 - Move start of remaining parts before status date forward to status
date
2a - And move end of completed parts forward to status date
In testing out the behavior of the task finish dates under the various
scenarios that these 4 checkboxes create, I have not been able to find
100% consistency with the status date results. I have found that no
combination of the past, current, and future start and finish dates
create results where if I mark all the milestones complete in PWA and
then incorporate the results using a start date set to a recent past
date (for example, 4/10/09), ALL the finish dates are updated to
4/10/09. In the scenario that almost passed, when all 4 boxes are
checked, one scenario still fails:
Past Start date/Current Finish date: The finish date at the resource
level is equal to the status date (4/10/09) but the task-level finish
date does NOT equal status date. The finish date at the task level is
updated to 4/17/09 (current date, not the status date).
This same scenario fails when more then one resource is assigned to it
and both mark the milestone 100% complete.
This is all very difficult to explain, but perhaps I just don't
understand the behavior of each well enough to determine how it is
generating the finish dates. Can you provide any insight into how
this would work best?
Thanks!