59
Using Project Server 2010 for Demand Management and Collaboration January 19 th , 2011

Project Server 2010 for Demand Management

Embed Size (px)

DESCRIPTION

Using Project Server 2010 for Demand Management and Collaboration

Citation preview

Page 1: Project Server 2010 for Demand Management

Using Project Server 2010 for

Demand Management and

Collaboration

January 19th, 2011

Page 2: Project Server 2010 for Demand Management

Speaker Biography

Daniel Bell, PMP, MCP, MCTS,

• Managing Director at MS PROJECT NOW!,

• Life-long consultant with a very strong background in

many technical disciplines, as well as a strong

functional background.

Page 3: Project Server 2010 for Demand Management

• MS PROJECT NOW! is a full service Microsoft Portfolio and Project Management (PPM) consulting firm.

• Collectively, we have over 40 years of experience. We have successfully delivered nearly 100 implementations.

• We deploy complete end-to-end solutions built to handle our clients’ current and future needs.

We deliver value with integrity and honesty.

We are committed to results and client satisfaction.

MS PROJECT NOW!

The MPN Story

Page 4: Project Server 2010 for Demand Management

Demand Management with Project Server 2010

– Overview of Demand Management

– Business Drivers

– Portfolio Analysis

• Demand Management Components

– Enterprise Project Types

– Project Workflows

– Project Detail Pages

– Approvals

– Steps to Implement

Microsoft Project Server 2010

4

Page 5: Project Server 2010 for Demand Management

Key benefits of Project Server 2010

Page 6: Project Server 2010 for Demand Management

OVERVIEW OF

DEMAND MANAGEMENT

Page 7: Project Server 2010 for Demand Management

Unified Project and Portfolio Management Capture all work in a central repository

Page 8: Project Server 2010 for Demand Management

What is Demand Management?

Part of the overall Project Server 2010 solution

You can capture all work proposals in one single place

Workflows are a component of Demand Management which you can use to automate your existing business processes –optional, not required

You can create customized workflows as well as pages for displaying and collecting information from the end users

Workflows, along with other key concepts, are captured and integrated within the demand management feature set

Page 9: Project Server 2010 for Demand Management

Microsoft EPM Solution

Sample Phases of a Project Lifecycle

Enterprise Project Management

Manage

Collaboration & Reporting

Plan

Work Planning

Select

Portfolio Selection

Create

Demand Management

NOTE: Phases are custom tailored to the business needs, drivers, and governance

Page 10: Project Server 2010 for Demand Management

End User Experience

Simple to use

Information collected in stages

Information split into convenient sections/links

User Interface similar to SharePoint

Can create proposals without schedule ! Powerful and flexible

One place to enter various types of work

Enhanced support for templates

Ability to track initiatives from start to end

Align demand requests with strategy

Standardized deployment, maintenance

Page 11: Project Server 2010 for Demand Management

Business Drivers

Definition

Business Drivers

Prioritization

Aligning Projects/Proposals

to Business Drivers

Projects/Proposals Prioritization

Portfolio Analysis (cost, resource)

Process Overview

Page 12: Project Server 2010 for Demand Management

Business Drivers

Page 13: Project Server 2010 for Demand Management

Business Driver

• Business Drivers represent an organization’s business objectives in Project

Server 2010

• Create drivers in the Business Driver Library

• May be associated with zero or more Departments

• Drivers are prioritized to reflect organization’s perceived business impact and

importance

Page 14: Project Server 2010 for Demand Management

Calculated Driver Prioritization

System calculates the consistency ratio

Inconsistent prioritizations may make sense in some instances but should be

reviewed carefully

Page 15: Project Server 2010 for Demand Management

Driver A Driver B Driver C Driver D

Driver A 1 9 6 1

Driver B 1/9 1 3 1/6

Driver C 1/6 1/3 1 1/3

Driver D 1 6 3 1

Driver A Driver B Driver C Driver D

Driver A 1 9 6 1

Driver B 1 3 1/6

Driver C 1 1/3

Driver D 1

Driver A Driver B Driver C Driver D

Driver A 9 6 1

Driver B 3 1/6

Driver C 1/3

Driver D

Driver A Driver B Driver C Driver D

Driver A Extremely More Strongly More Equal

Driver B Moderately More Strongly Less

Driver C Moderately Less

Driver D

Fill the systemic matrix with the pairwise values

Calculate eigenvector for the matrix

Normalize eigenvector values to 100% to derive relative

priorities

Algorithm

Page 16: Project Server 2010 for Demand Management

www.msprojectnow.com

Demo: Business Driver Prioritization

Page 17: Project Server 2010 for Demand Management

Portfolio Analysis

Page 18: Project Server 2010 for Demand Management

Portfolio Analyses

Portfolio analyses are a collection of projects that will compete for selection

based on their cost relative to their strategic value

Prioritization of Projects:

By Business Drivers

By Custom Field

Page 19: Project Server 2010 for Demand Management

Project Interdependencies

Project dependency relationship will be respected during portfolio selection scenario calculations There are following types of interdependencies:

Dependency: If Project A selected, Project B must be selected Mutual Inclusion: For a set of projects, if one project is selected, all projects in the set must be selected. Mutual Exclusion: For a set of projects, only one project in the set can be selected (Alternatives). Finish to Start: Used in Resource Constraint Analysis for identifying scheduling constrains

Page 20: Project Server 2010 for Demand Management

Cost Constraint Analysis

Page 21: Project Server 2010 for Demand Management

The need for optimization

Value Cost

Project 1 30% $100

Project 2 20% $60

Project 3 15% $40

Value Cost

Project 1 30% $100

Project 2 20% $60

Project 3 15% $40

Page 22: Project Server 2010 for Demand Management

Force In/Out

A portfolio may contain projects that must be either selected or not selected,

regardless of their cost/value ratio or their dependencies on other projects.

Aliases available for “Force In/Out” per analysis

Examples:

A non-strategic project that must be implemented because of legal

compliance issues will need to be “forced in” the portfolio.

A very costly project might need to be “forced out” of a portfolio to free up

resources for other projects and improve the portfolio’s overall ROI

Page 23: Project Server 2010 for Demand Management

www.msprojectnow.com

Demo: Cost Constrained Analysis/Force-in

Page 24: Project Server 2010 for Demand Management

Resource Constraint Analysis

Page 25: Project Server 2010 for Demand Management

Resource Constraint Analysis

Simplified Algorithm – Resource

Allocation

• Portfolios may also be analyzed by their high-level resource requirements

combined with their prioritization

• Higher priority projects are resourced first, lower priority projects are

resourced last.

• If resource availability does not meet a given project’s demand for any period

for any role, that project is not resourced and the project with the next lowest

priority is examined

Page 26: Project Server 2010 for Demand Management

www.msprojectnow.com

Demo: Resource Constrained Analysis

Page 27: Project Server 2010 for Demand Management

What’s Next?

Page 28: Project Server 2010 for Demand Management

Portfolio Comparison

Portfolio selections scenarios should be adjusted and recalculated until a

scenario is reached that should be finalized or compared with other scenarios

Portfolios may be compared with each other by:

Projects Selected

Strategic Value

Custom Fields (example: ROI )

Page 29: Project Server 2010 for Demand Management

Commit Portfolio Analysis

Decisions Once you have completed your portfolio analysis, the final step is to commit your

portfolio

Optionally, committed portfolios may kick off a workflow

Page 30: Project Server 2010 for Demand Management

www.msprojectnow.com

Demo: Compare Anlaysis

Page 31: Project Server 2010 for Demand Management

Demand Management Concepts

Page 32: Project Server 2010 for Demand Management

Demand Management Concepts

Enterprise Project Types

Workflows

Stages/Phases

Project Detail Pages

SharePoint/Custom Web-parts

Enterprise Custom Fields

Page 33: Project Server 2010 for Demand Management

ENTERPRISE PROJECT TYPES

(EPTs)

Page 34: Project Server 2010 for Demand Management

Enterprise Project Type (EPT)

Enables project creation with template schedule, workflow,

and workspace

Blueprint for creating a Proposal

Groups these components:

Project Server Workflows

Project Details Page (PDP)

Stages

Phases

Project Plan Template

Project Site Template

Department

Out-of-the-Box EPTs Sample Proposal - Workflow driven

Basic Project Plan - Non workflow driven

Page 35: Project Server 2010 for Demand Management

Demo: EPTs

Page 36: Project Server 2010 for Demand Management

PROJECT WORKFLOWS

Page 37: Project Server 2010 for Demand Management

Project Server Workflows

Not all EPTs require workflows

Allows for a custom approval process

Workflow supports:

Simple Project Lifecycle (single stage/approval)

Complex Project Lifecycle (multi-stage/approval)

Overlaid on SharePoint Workflows

Create Custom Workflows created in Microsoft®

Visual Studio® 2010 (SharePoint Designer is NOT

supported)

Page 38: Project Server 2010 for Demand Management

Changing an EPT mid-lifecycle

A project or proposal’s EPT may be changed in mid-lifecycle if necessary

Current workflow will end and new EPT’s workflow will begin

New EPTs pages will be loaded

Save current page’s data prior to changing EPT

Page 39: Project Server 2010 for Demand Management

STAGES

Page 40: Project Server 2010 for Demand Management

Workflow Stages

• Represents one step

within a project lifecycle

• Appears as steps at the

End-User level

• Controls the behavior

of:

– Visible PDPs

– Read-Only/Required

Custom Fields

– Associated Phase

Out-of-the-Box Stages

Page 41: Project Server 2010 for Demand Management

PHASES

Page 42: Project Server 2010 for Demand Management

Workflow Phases

• Collection of Stages grouped together to identify a

common set of activities in the project life cycle

• Used as a placeholder – Typically used for identification purposes

– Group Stages together

• Phases do not directly affect Project Detail Pages

For example,

A phase is like an empty file

folder with a name on the tab

Out-of-the-Box Phases

Page 44: Project Server 2010 for Demand Management

OOB Sample Proposal Workflow

Custom Fields supporting OOB workflow: Sample Approved Finish Date

Sample Approved Start Date

Sample Areas Impacted

Sample Assumptions

Sample Business Need

Sample Compliance Proposal

Sample Goals

Sample Post Implementation Review Date

Sample Post Implementation Review Notes

Sample Primary Objectives

Sample Proposal Cost

Sample Proposed Finish Date

Sample Proposed Start Date

Lookup Tables supporting OOB workflow: Sample Areas Impacted

Sample Primary Objective

Page 45: Project Server 2010 for Demand Management

Visualizing Project Workflow

Two OOB Excel report templates are available that

help you to visualize Projects as they go through

workflow stages and phases: WorkflowChart

WorkflowDrillDown

Page 46: Project Server 2010 for Demand Management

Demo: Workflow Reporting

Page 47: Project Server 2010 for Demand Management

PROJECT DETAIL PAGES

Page 48: Project Server 2010 for Demand Management

Project Details Page (PDP) SharePoint Web Part page that is used

to drive the project lifecycle

– Used to input and/or view data

– Can add other SharePoint Web Parts

– Includes project fields

– Can be reused for other Stages

– Is “project” aware

– Library of PDPs can be used across

multiple EPTs/Stages

Out-of-the-Box PDPs

Post-Implementation Review Project Details Project Information

Proposal Details Proposal Schedule Proposal Stage Status

Proposal Summary Schedule Strategic Impact

PDPs

Page 49: Project Server 2010 for Demand Management

Demo: PDPs

Page 50: Project Server 2010 for Demand Management

APPROVALS

Page 51: Project Server 2010 for Demand Management

Workflow Approvals

PWA -> “Workflow Approvals” in the Approvals section of Quick Launch

The approval process allows decision-makers :

Ability to tightly control which projects continue along in their

lifecycle

Provide input to people who are submitting the project proposals

Project Server Workflow Tasks

Items requiring review and approval displayed

Edit Item to comment and make an approval/rejection decision

Approver may be notified by email

“Edit this task” on the message in Outlook

Default WF approvers in PWA (security

group):

Portfolio Managers

Page 52: Project Server 2010 for Demand Management

Approval Configuration

Typically approvals are placed between

Stages and Phases

Stages and Phases do not necessarily

have to have approvals to proceed

Approval Process is based on SharePoint

Server 2010

Page 53: Project Server 2010 for Demand Management

STEPS TO IMPLEMENT

Page 54: Project Server 2010 for Demand Management

Step 1: Define the Project Lifecycle

Page 55: Project Server 2010 for Demand Management

Step 2: Define the Workflow Phases Create

Phase

Select

Phase

Manage

Phase

Finished

Phase

Plan

Phase

Page 56: Project Server 2010 for Demand Management

Step 3: Create and Configure Objects In Project Web App

Custom Fields (Project/Task/Resources)

Phases

Stages

Project Detail Pages

Project Plan Template*

Project Site Template*

Enterprise Project Type (EPT)

* Optional

Page 57: Project Server 2010 for Demand Management

Step 4: Create Workflow in Visual Studio Requirements to create Project Server Workflows

– Must be installed on the same box as Project

Server

InfoPath Services, Excel Services …)

IMPORTANT

Please refer to the MSDN SDK and webcasts for

guidance/samples and Step by Step instructions

on Workflow and Demand Management

Page 58: Project Server 2010 for Demand Management

Summary

• Project Server 2010’s Demand

Management:

– Supports Work Management and

governance

– Unifies project and portfolio

management

– Flexible and extensible

– Build on SharePoint Server 2010

Page 59: Project Server 2010 for Demand Management

Thank you for your consideration of MS PROJECT NOW! At MS PROJECT NOW! we believe in outstanding customer service. This is why we will always ensure expectations are properly set and maintained throughout every client relationship. We also consider trust a necessity, and therefore we will never mislead or misstate anything to our clients. This is because we believe in building and maintaining long-lasting relationships with you and your organization. Contact Information: Sherry Lucia Director, Client Relationships Mobile: 603.490.4124 [email protected]