Change in Baseline start and start

[Girija]

Hello,

I was viewing a project and found that there is difference in Baseline start
and start, while actual start is NA. Could anyone help me to to understand as
why there is change in the Baseline Start and Start?

Does it mean that after the project is Baselined th eProject Owner has
changed?
If so is there any way that we can rebaseline with the same date?

Thanks

Girija

 

[Girija]

Sorry missed one more point.

Also if any of the tasks is updated, how this rebaseline will impact?

Thanks

Girija

 

[Gary L. Chefetz [MVP]]

Girija:

It simply means that the current "planned" start is later than the
"baseline" start. One might assume that the project manager changed the
start date of the plan. Yes, you can simply re-baseline the project
overwriting the current baseline.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Dale Howard [MVP]]

Girija --

If there is a difference between the Baseline Start date and the Start date,
there could be a variety of reasons for this. If a predecessor task slipped
after the PM enters actuals, successor tasks will slow the slippage with a
Start date later than their Baseline Start date. Or as you surmised, the PM
has revised the schedule after baselining the project. I'm curious why you
want to rebaseline the project now. Microsoft Project calculates all
variance in the project against the Baseline, so if you rebaseline the
project, you lose all variance. Let us know.

 

[/pd]

"Microsoft Project calculates all

variance in the project against the Baseline"

I use multiple baseline setting when I change item(s)..this helps in phasing
in/out portions of the project and help tracks health state... between phases.

Not sure, is anyone else using a similar technique and pub'ing into PWA and
if there is anyother method that I could use ?

FYI.. using PS07

/pd

 

[Dale Howard [MVP]]

/pd --

Remember that Microsoft Project calculates all variance against the Baseline
set of fields. It DOES NOT calculate variance using any of the Baseline1 -
Baseline10 sets of fields. Because of this, we recommend that the Baseline
set of fields always contains your CURRENT baseline for the project. When
you need to rebaseline your project, due to a major change control procedure
for example, we recommend that you first BACK UP the Baseline set of fields
into one of the other sets, such as Baseline1, and then you rebaseline your
project as needed. By the way, backing up a baseline is not obvious. To do
this, complete the following steps:

1. Click Tools - Tracking - Set Baseline (or Save Baseline in earlier
versions of Microsoft Project).
2. In the Baseline dialog, select the Set Interim Plan option (Save Interim
Plan in earlier versions).
3. Click the Copy pick list and select the Baseline item.
4. Click the Into pick list and select the Baseline1 item (or any other
alternate Baseline set of fields).
5. Click the OK button.

This process copies all baseline values from the Baseline set of fields into
the Baseline1 set of fields. After backing up the Baseline, you are free to
rebaseline the project. Hope this helps.

 

[/pd]

Dale

Yes, thats I way I do it too. The only differene is that in the reporting
cube, I suck back , base#1 and base#2 and so on for calc on costs..so the
differene between Actual vs BaseLine Vs Base#(n) can be noted and accordingly
histroical trending can be used for the next baseline / Phase (?).

Maybe I am being too nerdy and trying to use historical data from the
project applied it once again to the same project ?? and yes, I am
experimenting.meshing together with agile methods / PSP07 and Escrumv1.0
and (mabe) tieing in VTFS i