Tagged: start variance nonzero
I’m using 4 sub-projects and I’ve just reset Baseline 1. To do this I selected every record in the project and under Schedule I SET BASELINE…>For:Selected Tasks>Roll up baselines: To all summary tasks, From subtasks into selected summary tasks. I would expect the Start and Finish Variances to be zero for every task in the project which has not yet started. Instead, I see many tasks with non-zero variance values. Why might that be?
Dan, instead of saving selected tasks try doing a complete baseline to baseline1 again (rebaseline Baseline1).
Apparently that doesn’t work for sub-projects. Only the tasks in the master project get baselined.
…that being said, the problem is that start and finish variance is computed using Baseline, never Baseline N. Is there a way to save Baseline into one of the Baseline N slots for safekeeping?
Dan you’re correct. I missed the read of the numbered baseline and variance…oops Standard practice for me (and I say me because baseline standards aren’t consistent between those who write about it), is to always use Baseline as your “current” baseline. Baseline1 is your first baseline, baseline2 is the baseline of your next stagegate, and so forth. That way you can compare baselines over time.
Every time you reset a complete baseline you do it to Baseline and the next numbered baseline. Then you update Baseline with selected tasks when you have minor change requests or additional tasks. Hope that makes sense.
You can copy a baseline to any other baseline by using the Set Interim Plan option within the Set Baseline dialog. For your question above, select Baseline in the Copy field and Baseline’n’ in the Into field. Good luck…
>>You can copy a baseline to any other baseline by using the Set Interim Plan option within the Set Baseline dialog. For your question above, select Baseline in the Copy field and Baseline’n’ in the Into field. Good luck…
That is truly inspired UI design! That would have never occurred to me in a millennium. Thank you!
FYI, baselines for inactivated tasks are not saved to the destination when doing this.