Demand Management Configuration in Project Server 2010

Use project detail pages (PDPs) with workflows and custom fields to customize Project Server for project-creation, from ides, proposals, change requests or even bug tracking. PDPs are Web Part pages; they are built with the SharePoint Server infrastructure to show or edit details of entities for Project Management such as project meta data, resources, schedule, or strategic impact and any other unique custom process. Project Server 2010 enables users to create an unlimited number of pages and to control exactly what project data is available on each page. You can customize PDPs by using Web Parts and a ribbon interface, provide Quick Launch navigation specific to project data, and dynamically filter custom fields by departmental association.

PDPs can integrate many project management scenarios, such as the following:

  1. Assessing project impact of strategic objectives.
  2. Providing workflow-driven capture of details in project proposals or business process ideas etc..
  3. Providing workflow-driven executive buy-in before proceeding further.
  4. Performing portfolio analyses based on cost and resource capacity constraints.

You can create three kinds of PDPs in PWA.

  1. Project Used for editing project details in a non-workflow enterprise project template, or in other applications.
  2. New Project Used for creating a project. This type of PDP is required with an enterprise project template that has a workflow for portfolio analysis.
  3. Workflow Status Shows the current stage and status for a project proposal.
  4. Go here to Create a PDP http://ps.rlan.ca/pwa/Project%20Detail%20Pages/Forms/AllItems.aspx. Use the Documents tab of the page to create a PDP.

Project Server 2010 includes the following new Web Parts for PDPs:

  1. Buttons Web Part Enables users to edit, save, publish, or close a project detail page, or to move to the next stage in a workflow. A long page can include multiple Buttons Web Parts.
  2. Workflow Status Web Part Enables users to check the status of Project Server workflows.
  3. Project Fields Web Part Enables users to select or edit project custom fields for the PDP. Project summary task fields such as cost and actual work are read-only. Custom fields such as the project name, department, managing workflow, start date, and owner are read/write.
  4. Strategic Impact Web Part Includes all business driver definitions filtered by one or more departments. This Web Part enables users to rate the project impact on each driver.
  5. Dependencies Web Part Enables users to define dependencies between projects.

For a code example, see Walkthrough: Creating a Project Server Web Part with a JS Grid.

Advertisements