Project Workspace - Issues / Risks Priority vs. Tasks priority

[anovak]

Any reason why MS supplied (1) High (2) Medium (3) Low for Issue/Risk
priorities and (1) High (2) Normal (3) Low for Task priority? Are
most of y'all changing the (2) Normal to (2) Medium to match the
Issue and Risk priority attributes?

Again, just curious.

Thanks
Andy Novak
UNT

 

[Gary Chefetz]

Andy:

You're comparing apples to donuts. Different developers. Anyway, tasks do
have "normal" priority. I'm not prepared to "normalize" risks and issues.
How about you?

 

[anovak]

Andy:

You're comparing apples to donuts. Different developers. Anyway, tasks do
have "normal" priority. I'm not prepared to "normalize" risks and issues.
How about you?

--
Gary L Chefetz, MVP, MCT, MCITP
msProjectExpertshttp://www.msprojectexperts.com
FAQs and Referencehttp://www.projectserverexperts.com
BLOG:http://projectserverhelp.com

It just doesn't make sense to me unless there's some reason for it.
It just confuses users and I'd rather have the priority terminology be
consistent in the workspace unless there is an internal reason to
leave it alone (like the Status field for Issues, etc.)

 

[Gary Chefetz]

Andy:

By all means, change it in the workspace.

 

[anovak]

Andy:

By all means, change it in the workspace.

--
Gary L Chefetz, MVP, MCT, MCITP
msProjectExpertshttp://www.msprojectexperts.com
FAQs and Referencehttp://www.projectserverexperts.com
BLOG:http://projectserverhelp.com

Any reason I shouldn't change the values of the Task Status field
(keeping in mind the Issues Status field values cannot be changed)?
I've thought about adding the (1), (2), number sequencing as a prefix
to the values provide by Microsoft

 

[Rod Gill]

While you're at it, I use % for likelihood and predict impact 3 ways: $ time
and work. This way % chance * $ is cost contingency required, time * % is
contingency time needed and Work * % is contingency resource effort needed
for the project.

EG supplier may miss ship leaving port date and so cause a weeks delay until
the next ship. This may then become a Risk:

Shipment late % chance 20%, $ cost $0, time 5d, Work 0h

There a delay contingency of 1d is required. Obviously that delay could
cause other costs, so adjust them as appropriate.

This model gives a much more useful contingency calculation as it's based
directly on remaining risk.

--

Rod Gill
Microsoft MVP for Project - http://www.project-systems.co.nz

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

Any reason I shouldn't change the values of the Task Status field
(keeping in mind the Issues Status field values cannot be changed)?
I've thought about adding the (1), (2), number sequencing as a prefix
to the values provide by Microsoft

__________ Information from ESET Smart Security, version of virus
signature database 4888 (20100222) __________

The message was checked by ESET Smart Security.

http://www.eset.com

__________ Information from ESET Smart Security, version of virus signature database 4888 (20100222) __________

The message was checked by ESET Smart Security.

http://www.eset.com