WANTED: The Pros & Cons of Multiple MS Project Baselines

[BGT]

I'd really like to collaborate with some of the experts here regardin
the use of the 11 Baselines contained in the 2007 version. What I'
specifically like to discuss is the use of the multiple baselines, I'v
read what they recommend them for but practically I'd like to hear you
opinions on the use of multiple baselines from a project management bes
practices standpoint.

I for one believe you should save an original baseline for the entir
project once during the life of the project. Perform a backup of th
original baseline in of of the ten additional Baseline fields and the
rebaseline only unstarted tasks as required during the project
life-cycle which could be caused by customer changes, internal chang
requests, etc. The value of the original baseline should be paramoun
in benchmarking variances from planned to current project status. I d
not see the purpose of having 10 other baselines, you wouldn't use on
new baseline per Change Request, there isn't enough Baselines in M
Project for that nor would it make sense. So what else would you us
the other Baselines for? "What-If" scenarios? It just seems to mak
more sense to "File Save As" for What-If's.

Appreciate your feedback and collaboration

 

[Dale Howard [MVP]]

BGT --

The biggest problem with using the 10 additional Baseline sets of fields
(Baseline1 - Baseline10) is that all project variance (Start, Finish,
Duration, Work, and Cost) is calculated using the data in the Baseline set
of fields. Furthermore, there is no way to force the software to calculate
variance using the data in the other 10 sets of Baseline fields. Think
about how much of a limiting factor this is!

Therefore, we recommend to our clients exactly the process that you espouse,
which is:

1. After a major change control procedure, back up your information in the
Baseline set of fields into one of the 10 additional sets, such as
Baseline1.
2. Rebaseline your project using one of the four available methods of
rebaselining, one of which is to rebaseline only unstarted tasks.
3. Add a task Note on the Project Summary Task (Row 0) indicating the date
the project was rebaselined, the set of Baseline fields into which you
backed up the original Baseline, and the reason for rebaselining the
project.

I think you are only solid ground doing what you are doing currently. Hope
this helps.

 

[Rod Gill]

Hi,

I use a slightly different method. I save the baseline for phase1 in
Baseline1, phase 2 in baseline2 and so on. If I want variances I copy the
current baseline to Baseline0. If I have a time critical project I save
Baseline0 before updating each week so I can see whether I gained or lost
and where easily.

I'm not sure that any process is better than another, just that having a
process is important and that it meets your governance needs.

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com

 

[BGT]

Well Dale it's a small world, it's me Brett, I recently went to you
MSPS 2007 training in Manhattan. Thanks for the reply and tips, havin
gone through your book in detail regarding baselines, our discussion i
Manhattan regarding how multiple baselines work and my local efforts t
construct and conduct training for my group it's really great to have a
interactive forum to share experiences and collaborate like this.

My challenge involves bringing our scheduling group up to speed wit
the nitty gritty details of MS Project's full capabilities whil
educating Control Account Managers, Project Managers and Project Lead
at a level they will understand and use in the real world. That said
having one manageable baseline to benchmark and measure variances fro
seems from our Aerospace industry to be a "best-practice" approach, bu
I don't want to short change our guys by missing some unknown (on m
part) advantage of using multiple baselines.

Thanks,
Brett

;4142364']BGT --

The biggest problem with using the 10 additional Baseline sets o
fields
(Baseline1 - Baseline10) is that all project variance (Start, Finish,
Duration, Work, and Cost) is calculated using the data in the Baselin
set
of fields. Furthermore, there is no way to force the software t
calculate
variance using the data in the other 10 sets of Baseline fields.
Think
about how much of a limiting factor this is!

Therefore, we recommend to our clients exactly the process that yo
espouse,
which is:

1. After a major change control procedure, back up your information i
the
Baseline set of fields into one of the 10 additional sets, such as
Baseline1.
2. Rebaseline your project using one of the four available methods of
rebaselining, one of which is to rebaseline only unstarted tasks.
3. Add a task Note on the Project Summary Task (Row 0) indicating th
date
the project was rebaselined, the set of Baseline fields into which you
backed up the original Baseline, and the reason for rebaselining the
project.

I think you are only solid ground doing what you are doing currently.
Hope
this helps.

I'd really like to collaborate with some of the experts her regarding
the use of the 11 Baselines contained in the 2007 version. What I'd
specifically like to discuss is the use of the multiple baselines I've
read what they recommend them for but practically I'd like to hea your
opinions on the use of multiple baselines from a project managemen best
practices standpoint.

I for one believe you should save an original baseline for th entire
project once during the life of the project. Perform a backup o the
original baseline in of of the ten additional Baseline fields an then
rebaseline only unstarted tasks as required during the projects
life-cycle which could be caused by customer changes, interna change
requests, etc. The value of the original baseline should b paramount
in benchmarking variances from planned to current project status. do
not see the purpose of having 10 other baselines, you wouldn't us one
new baseline per Change Request, there isn't enough Baselines in MS
Project for that nor would it make sense. So what else would yo use
the other Baselines for? "What-If" scenarios? It just seems t make
more sense to "File Save As" for What-If's.

Appreciate your feedback and collaboration.


--
BGT
------------------------------------------------------------------------
BGT's Profile: http://forums.techarena.in/members/bgt.htm
View this thread http://forums.techarena.in/microsoft-project/1091766.htm

http://forums.techarena.in

 

[Dale Howard [MVP]]

BGT --

You are more than welcome, my friend!

Well Dale it's a small world, it's me Brett, I recently went to your
MSPS 2007 training in Manhattan. Thanks for the reply and tips, having
gone through your book in detail regarding baselines, our discussion in
Manhattan regarding how multiple baselines work and my local efforts to
construct and conduct training for my group it's really great to have an
interactive forum to share experiences and collaborate like this.

My challenge involves bringing our scheduling group up to speed with
the nitty gritty details of MS Project's full capabilities while
educating Control Account Managers, Project Managers and Project Leads
at a level they will understand and use in the real world. That said,
having one manageable baseline to benchmark and measure variances from
seems from our Aerospace industry to be a "best-practice" approach, but
I don't want to short change our guys by missing some unknown (on my
part) advantage of using multiple baselines.

Thanks,
Brett

;4142364']BGT --

The biggest problem with using the 10 additional Baseline sets of
fields
(Baseline1 - Baseline10) is that all project variance (Start, Finish,
Duration, Work, and Cost) is calculated using the data in the Baseline
set
of fields. Furthermore, there is no way to force the software to
calculate
variance using the data in the other 10 sets of Baseline fields.
Think
about how much of a limiting factor this is!

Therefore, we recommend to our clients exactly the process that you
espouse,
which is:

1. After a major change control procedure, back up your information in
the
Baseline set of fields into one of the 10 additional sets, such as
Baseline1.
2. Rebaseline your project using one of the four available methods of
rebaselining, one of which is to rebaseline only unstarted tasks.
3. Add a task Note on the Project Summary Task (Row 0) indicating the
date
the project was rebaselined, the set of Baseline fields into which you
backed up the original Baseline, and the reason for rebaselining the
project.

I think you are only solid ground doing what you are doing currently.
Hope
this helps.

I'd really like to collaborate with some of the experts here regarding
the use of the 11 Baselines contained in the 2007 version. What I'd
specifically like to discuss is the use of the multiple baselines, I've
read what they recommend them for but practically I'd like to hear your
opinions on the use of multiple baselines from a project management best
practices standpoint.

I for one believe you should save an original baseline for the entire
project once during the life of the project. Perform a backup of the
original baseline in of of the ten additional Baseline fields and then
rebaseline only unstarted tasks as required during the projects
life-cycle which could be caused by customer changes, internal change
requests, etc. The value of the original baseline should be paramount
in benchmarking variances from planned to current project status. I do
not see the purpose of having 10 other baselines, you wouldn't use one
new baseline per Change Request, there isn't enough Baselines in MS
Project for that nor would it make sense. So what else would you use
the other Baselines for? "What-If" scenarios? It just seems to make
more sense to "File Save As" for What-If's.

Appreciate your feedback and collaboration.


--
BGT
------------------------------------------------------------------------
BGT's Profile: http://forums.techarena.in/members/bgt.htm
View this thread: http://forums.techarena.in/microsoft-project/1091766.htm

http://forums.techarena.in

--
BGT
------------------------------------------------------------------------
BGT's Profile: http://forums.techarena.in/members/bgt.htm
View this thread: http://forums.techarena.in/microsoft-project/1091766.htm

http://forums.techarena.in