Analyze portfolio based on high-level cost constraints (Project Server 2010)
Applies to: Project Server 2010
Topic Last Modified: 2011-04-13
After you have created an analysis and reviewed the relative priority values of the proposals, the next step is to analyze the proposals based on high-level cost constraints. You can set cost limits that help narrow the list of proposals that can reasonably be approved as projects.
This article and the videos it contains describe a typical portfolio analysis scenario. Your organization may have customized this process to meet unique business needs.
On the Quick Launch, in the Cost Constraint Limits section, adjust the value of the primary cost constraint, and then click Recalculate.
To include additional constraints by using custom fields, under Cost Constraint Limits, click Add/Remove. Add the field, click OK, and then set the value for the field. Click Recalculate to see its effect on the scenario.
Click the Force in/out column for each row in the Projects table to choose to manually include or exclude a project in the scenario.
Type adjusted costs in the Projects table to evaluate what-if cost scenarios. Notify the proposal owner of the adjusted budget for the proposal, if this scenario is committed.
To override project dependencies for the scenario, on the Options tab, clear the Enforce Project Dependencies check box.
On the Analysis tab, click Save As and name the scenario.
Click Compare to review the saved scenarios.
Once you have completed these procedures, the next step is to analyze the portfolio based on time-phased resource requirements, if the proposals in your portfolio have resource information defined. If the proposals in your portfolio do not have resource information defined, the next step is to commit your selection decisions and communicate them to portfolio stakeholders.