Tuesday, January 12, 2010

Project Server 2010 Features - Part 3

Previous - Project Server 2010 Features Part 2 & Part 1

  • Workflow
    • Enterprise Project Types – this feature extends the potential of templates by also allowing differing workflows to be associated with different project types.
    • User configurable Workflows to manage your project lifecycle
    • Enhanced governance through workflow
    • The Project Server workflow platform is built on the SharePoint 2010 workflow platform, which in turn is based on the Windows Workflow Foundation.
    • Workflow is a key component of demand management.
    • A Project Server workflow runs on a Project Web Access site and helps to manage a sequence of activities or alternate sets of activities related to project management such as Check Project Custom Field Value and Publish Project.
    • Project Server 2010 workflows use the Site workflow paradigm, which removes the restriction that a WSS workflow can be started only on a list item. Project Server workflows are deployed to Project Web Access, and workflow instances can be run only as a project entity.
    • Project Server workflows must be created in Microsoft Visual Studio 2010. Project Server workflows cannot be created from Microsoft SharePoint Designer 2010.
    • The administration of Project Server workflows is identical to managing any other Windows SharePoint Services 2010 workflow. Workflow instances are created when a project is created and are deleted when the project is deleted/completed/rejected.
    • Unlike in WSS, a user does not start a workflow instance from the administration page.
    • Workflows are associated with stages. PDPs are not referenced within the workflow. The PDPs simply act as containers to hold or display data. The workflow can however, references custom fields in the Web Parts.
  • Resource Management
    • Resource Updating -Multiple places for resources to update their tasks now
    • Resource Capacity Planning
  • Integration & Synchronization
    • SharePoint synchronization
    • Increased collaboration
    • Exchange Server:
      • Team members can look and manage their tasks and statuses from Outlook, and mobile users can access their schedules and provide updates using Outlook Exchange for Mobile or Outlook Web Access
      • Replace the Outlook add-in with Exchange Server integration
    • Team Foundation Server
      • Development teams can continue to work within TFS on tasks and assignments and have updates synchronized with Project
      • Valuable for Application Lifecycle Management integrating Team Foundation Server
    • MS Dynamic - Out of the box integration with AX (ERP) and SL, so that SMBs can extend Project accounting applications
    • Portfolio Server - Integration of Portfolio Server into the Project Server environment (single system versus two separately deployed products for 2007)

Previous - Project Server 2010 Features Part 2 & Part 1

Cont... Project Server 2010 Features - Part 4

No comments: