Search Help:

About Project Priorities

The Priority field indicates the level of importance given to the project. The project priority is then used in calculating the risk score for the project. Projects with higher priority will be given a higher weighting in calculating the risk impact.

Priority levels range from 0% - 100%. The lowest priority is 0%. The default priority is 100%. Summary projects (programs) don’t have priorities.

Priorities can be changed in any Project view: Portfolio Gantt, Risked Projects, and Project Portfolio. You don’t need to open individual projects to change the project priority. You must have appropriate permissions to change a priority:

  • Administrators can change priorities for any project
  • Managers can change priorities in projects for which he/she has permisson
  • Users cannot change priorities

Project priorities are used in the following calculations:

  1. Project risk scores for non-schedule risks are multiplied on project priority.
  2. Risk impact is multiplied on project priority. Here is an example. The project with project priority 50% has a summary project: Automatic assignment.

Project Name Priority
Summary Project  
Project 1 50%

Project #1 has a risk assigned to it. For Project #1, the risk register would look like:
Risk Name Probability Impact Score
Risk 1 50% 80% 40%

A risk register with the same risk for a summary project would look like:
Risk Name Probability Impact Score
Risk 1 50% 40% 20%

The risk impact is multiplied on Project #1 priority = 50% for the summary project only.

Note: To reflect project priority in the risk impacts you should open, recalculate and save the project.

See also

Creating a Portfolio Hierarchy

Legal Notice Privacy Statement Copyright © Intaver Institute Inc., 2002-. All Rights Reserved.