Quick Links

Reply To: Best Practices for Baselining and Variance Analysis

Home Forums Discussion Best Practices for Baselining and Variance Analysis Reply To: Best Practices for Baselining and Variance Analysis

Larry Christofaro

Carlos, I didn’t see the webinar but the way you are explaining is not what I consider best practice. Some general thoughts:
1. Baseline should always be the most current baseline. Variance, EV calculations, and views all default to using Baseline.
2. Approved changes should update the Baseline using baseline selected tasks. You typically want to rollup changes, but take a close look at or read up on how to handle rollup options.
3. I tend to not baseline added tasks that aren’t a result of an approved change request. Some people will say to baseline but not rollup the baseline data, but I like the visibility of knowing these tasks are by default not budgeted.
4. On defined stage-gates that include a re-estimation, copy the baseline to Baseline1 (or another baseline), and reset Baseline with the now current baseline data.
5. If the project needs to be re-baselined outside of a regular stage-gate, use a baseline that is not used in your standard methodology.
There are variations, but you can see my point. I actually set my original baseline to both Baseline and Baseline1. Baseline1 is always the original baseline. Then set both Baseline and Baseline2 for the next stage-gate. Now Baseline1 is the original and Baseline2 is the stage-gate…etc. The baselines are cleaner that way.

BTW: use the Interim Plan option to copy a baseline to another baseline.
Hope that helps…