R
Rich E.
On occasion, I get an approved scope change to an in-flight phase of a
project. It can usually be represented by a new set of tasks. The
approved scope change allows me to change the baseline work for the
associated summary rows and the total project ... by just the amount
of the scope change only. I still need to live with the other
variances. The baseline-selected-tasks and roll-up-to-summary-tasks
works quite well for this process.... sometimes. Other times, I get
results in the overall project summary (row zero) that seem
unexplainable. Does anybody know the *exact* way that the calculation
takes place? i.e. does MS Proejct simply add the new baseline values
for the new tasks to all of the associated sumary rows?.. or is there
something deeper happening? Based on the strange results that I
sometimes get, I'm guessing that there is more to it. I notice that
the results are strangest when actuals have already been posted to the
plan.
project. It can usually be represented by a new set of tasks. The
approved scope change allows me to change the baseline work for the
associated summary rows and the total project ... by just the amount
of the scope change only. I still need to live with the other
variances. The baseline-selected-tasks and roll-up-to-summary-tasks
works quite well for this process.... sometimes. Other times, I get
results in the overall project summary (row zero) that seem
unexplainable. Does anybody know the *exact* way that the calculation
takes place? i.e. does MS Proejct simply add the new baseline values
for the new tasks to all of the associated sumary rows?.. or is there
something deeper happening? Based on the strange results that I
sometimes get, I'm guessing that there is more to it. I notice that
the results are strangest when actuals have already been posted to the
plan.