Setting Save Baseline to Deny: Baselines 1 to 10 Can Still be Sav

[Sir Ganttalot]

Anyone else noticed this oddity ("undocumented feature") in Project Server
2003?

It seems that setting a group or individual Global Permissions Save Baseline
permission to "Deny" only prevents a person from setting "Baseline", but
allows a user to save Baselines 1 to 10 without any restrictions. I see both
adbvantages and drawbacks to this. It all depends on how you pitch it to
your user base.

Anyway, if someone could validate that what I am seeing is the same in other
environments I would be interested to hear. Many thanks.

 

[Dale Howard [MVP]]

Sir Ganttalot --

Yes, I believe this feature is by design and is not a bug. The Baseline
information saved in the Baseline 1 to Baseline 10 sets of fields does not
display by default in the Tracking Gantt view, or in the Work, Cost, or
Variance tables. Therefore, this feature allows an organization, such as a
PMO, to reserve the right to set the working Baseline for the project, while
allowing a PM to save his/her own personal Baselines for the project in the
alternate 10 sets of fields. Hope this helps.

 

[Sir Ganttalot]

Thanks Dale for confirming that this is a design feature. I agree that this
can be presented as a useful capability, i.e. reserving one baseline for just
the PMO, but leaving the others available to the PM. And of course these
additional baselines can be associated with custom bars on a Gantt chart. I
would prefer of course to have control over how many are reserved for the
PMO, how many for the PM, but this is workable anyway.

Do you know if this changes in 2007?

--
Sir Ganttalot

Coming soon to YouTube

Sir Ganttalot --

Yes, I believe this feature is by design and is not a bug. The Baseline
information saved in the Baseline 1 to Baseline 10 sets of fields does not
display by default in the Tracking Gantt view, or in the Work, Cost, or
Variance tables. Therefore, this feature allows an organization, such as a
PMO, to reserve the right to set the working Baseline for the project, while
allowing a PM to save his/her own personal Baselines for the project in the
alternate 10 sets of fields. Hope this helps.

 

[Dale Howard [MVP]]

Sir Ganttalot --

I have not explored this in depth, but I don't think it is different in
Project Server 2007. Hope this helps.

Thanks Dale for confirming that this is a design feature. I agree that
this
can be presented as a useful capability, i.e. reserving one baseline for
just
the PMO, but leaving the others available to the PM. And of course these
additional baselines can be associated with custom bars on a Gantt chart.
I
would prefer of course to have control over how many are reserved for the
PMO, how many for the PM, but this is workable anyway.

Do you know if this changes in 2007?

--
Sir Ganttalot

Coming soon to YouTube

 

[Khurram Jamshed]

Hi Dale,
my google search brought this thread as result to me, so i though would be better if i open the same instead of creating new thread

I couldn't understand the concept, that if i have an option to deny any change to project baseline (protected/not-protected both), then why users belongs to the group are able to change it manually? i.e. user is not allowed to SET THE BASELINE of the project, but apparently he is allowed to change the baseline by manually entering the same value as planned to the baseline field.

imagine the customer has a simple request to not to let their users change the baseline values, and only PMO is allowed to do so based on the approved change request. this fairly is a realistic requirement, but unable to be accomplished.

could you please explain the purpose of such design?so that i will educate my client to understand the idea behind this behavior.

many thanks.

Anyone else noticed this oddity ("undocumented feature") in Project Server
2003?

It seems that setting a group or individual Global Permissions Save Baseline
permission to "Deny" only prevents a person from setting "Baseline", but
allows a user to save Baselines 1 to 10 without any restrictions. I see both
adbvantages and drawbacks to this. It all depends on how you pitch it to
your user base.

Anyway, if someone could validate that what I am seeing is the same in other
environments I would be interested to hear. Many thanks.

--
Sir Ganttalot

Coming soon to YouTube

On Thursday, June 28, 2007 5:35 PM Dale Howard [MVP] wrote:
Sir Ganttalot --

Yes, I believe this feature is by design and is not a bug. The Baseline
information saved in the Baseline 1 to Baseline 10 sets of fields does not
display by default in the Tracking Gantt view, or in the Work, Cost, or
Variance tables. Therefore, this feature allows an organization, such as a
PMO, to reserve the right to set the working Baseline for the project, while
allowing a PM to save his/her own personal Baselines for the project in the
alternate 10 sets of fields. Hope this helps.




news:[email protected]...

 

[Khurram Jamshed]

Hi Dale,
my google search brought this thread as result to me, so i though would be better if i open the same instead of creating new thread

first this scenario is same in PS2007 and PS2010.

I couldn't understand the concept, that if i have an option to deny any change to project baseline (protected/not-protected both), then why users belongs to the group are able to change it manually? i.e. user is not allowed to SET THE BASELINE of the project, but apparently he is allowed to change the baseline by manually entering the same value as planned to the baseline field.

imagine the customer has a simple request to not to let their users change the baseline values, and only PMO is allowed to do so based on the approved change request. this fairly is a realistic requirement, but unable to be accomplished.

could you please explain the purpose of such design?so that i will educate my client to understand the idea behind this behavior.

many thanks.

Anyone else noticed this oddity ("undocumented feature") in Project Server
2003?

It seems that setting a group or individual Global Permissions Save Baseline
permission to "Deny" only prevents a person from setting "Baseline", but
allows a user to save Baselines 1 to 10 without any restrictions. I see both
adbvantages and drawbacks to this. It all depends on how you pitch it to
your user base.

Anyway, if someone could validate that what I am seeing is the same in other
environments I would be interested to hear. Many thanks.

--
Sir Ganttalot

Coming soon to YouTube

On Thursday, June 28, 2007 5:35 PM Dale Howard [MVP] wrote:
Sir Ganttalot --

Yes, I believe this feature is by design and is not a bug. The Baseline
information saved in the Baseline 1 to Baseline 10 sets of fields does not
display by default in the Tracking Gantt view, or in the Work, Cost, or
Variance tables. Therefore, this feature allows an organization, such as a
PMO, to reserve the right to set the working Baseline for the project, while
allowing a PM to save his/her own personal Baselines for the project in the
alternate 10 sets of fields. Hope this helps.




news:[email protected]...