Monday, January 11, 2010

Project Server 2010 Features - Part 2

Previous - > Project Server 2010 Features - Part 1

  • Portfolio & Project Management
    • Web-based project editing
    • Unified Project and Portfolio Management (PPM) - Project Server unifies project and portfolio management capabilities in a single server providing a consistent user experience, common data store and centralized administration. It provides powerful new portfolio prioritization and selection analytics, project capture and initiation, and resource capacity planning.
    • Enterprise Project Types – this feature extends the potential of templates by also allowing differing workflows to be associated with different project types.
    • Departmentalization - Manage your business projects, resources and reporting by department/division/unit! this feature means that you can create projects where the custom fields are specific to a particular area of the business – for example an R&D project could report against totally different criteria to a project being undertaken by the HR or sales functions of an organization.
    • Portfolio Analysis - In Project Server 2010, a rich set of new Portfolio Strategy features are now available in the core Project Server product serving to more closely unify project and portfolio management
      • UI is now SharePoint-based, making these features easier to use and provides visual consistency with the rest of the app
      • A gateway linking the Portfolio Server product is no longer required, everything resides with one product
      • Full API support now available for these features via the Project Server Interface (PSI), and some integration with the Reporting Database (RDB).
      • Resource Analysis
        • Enables portfolio-level project scheduling and analysis based on organizational resource availability.
        • The Resource Plan feature can be used to specify high-level project resource requirements to be fed into the new Resource Analysis feature.
        • The new Resource Analysis feature helps you identify gaps in demand vs. availability, favoring higher priority projects for selection.
      • Organizations define and prioritize their strategic objectives, or business drivers.
      • Cost Analysis
        • Costs and resource requirements are assigned to each project proposal, and a proposal’s impact on each business driver is rated, generating relative project value/priority score across a portfolio.
        • The Portfolio Cost Constraint Analysis engine selects projects that yield the most value with the lowest cost, while the Resource Constraint Analysis feature chooses higher priority projects based on resource availability within a planning period’s timeline.
        • Given a limited budget, the Cost Analysis algorithm will select a portfolio that maximizes strategic value while minimizing cost

  • Demand Management
    • Demand Management is about capturing all work proposals in one single place, taking these proposals through a multi-stage governance process, making decisions on which proposals to approve and tracking progress on their execution until the work is completed. A key component within Demand Management is the Workflow governance model.
    • The Demand management functionality in Microsoft Project Server 2010 is designed to be both flexible and usable. It has a full-fledged governance workflow behind it.
    • Demand management Project Life cycle - A project lifecycle is a long-running process that spans various governance phases like create, select, plan, and manage. Within each phase are stages. Each stage can have an associated project detail page (PDP) in Project Web Access (PWA). The entire collection of stages represents a single workflow that can be linked to an enterprise project template (EPT).
      • Enterprise Project Type (EPT) - represents a wrapper that encapsulates phases, stages, a single workflow, and PDPs. Normally, project types are aligned with individual departments, e.g. Marketing/IT/HR projects. Using project types helps to categorize projects within the same organization that have a similar project life cycle.
      • Phases - Represent a collection of stages grouped together to identify a common set of activities in the project life cycle. Examples project creation, selection, and management. Phases provide a option of organizing stages into logical groups.
      • Stages - Represents one step, where data is manipulated before move to the next step, within a project lifecycle. A stage is composed of one or more project detail pages (PDPs) linked by common logic or theme. At each step, data must be entered, modified, reviewed, or processed.
      • Project Detail Pages (PDP) -A PDP represents a single Web Part Page in Project Web Access, used to display or collect information from the user.
      • Webpart - Project Server Web Parts and custom Web Parts used in demand management all contain custom fields. Web Parts can make calls to the PSI, query the reporting database, or integrate with external systems.
    • Governance Workflow - Workflow models the governance processes and provides a structured way for projects to proceed through the phases. Workflows are captured and integrated within the demand management feature set, providing a rich and dynamic platform. A governance workflow is all about creating a rich life cycle for any proposal/demand that comes into the system. It includes
      • defining the various stages through which the project goes in its lifecycle
      • Determining what information is required or locked at what stage including any manual approval/notifications steps as necessary and adding any business logic to update other Line of Business Systems.

Previous - > Project Server 2010 Features - Part 1

Cont... Project Server 2010 Features - Part 3

No comments: