consolidated_project_plan.docx

Hewlett-Packard Development Company, LP.

HP Restricted

Consolidated Project Management Plan

Project Management Plan

Project Name

Customer Name

Prepared By: Name/Organization

Saved 27-Mar-2015 HP Restricted Page 2 of 34

© 2014 Hewlett-Packard Development Company, L.P. All rights reserved.

document.docx


Document Information

© Copyright 2014 Hewlett-Packard Development Company LP.

This document is the property of, and confidential to Hewlett-Packard (HP) and all copyright is used

under license by HP. All information contained in this document, or acquired in connection with this

document, is confidential to HP and reproduction, adaptation or translation without prior written

permission is prohibited, except as allowed under the copyright laws. It may be disclosed within the

Client organisation only to those of its employees who are directly involved in the project to which this

document relates for the purpose of evaluating this document. The client will be solely and wholly

responsible for ensuring all such employees are aware of and abide by this condition. This is at all

times subject to what is agreed in the contract(s) between the parties.

Project Name:

Document Contact

Name

Title

Mobile

Email

Desk Telephone

Version History

Document Status (e.g. Draft, Final, Release #):

Ver. No.

Ver. Date

Revised By Description

Distribution

Name Title Reason(Review, Approve,

Inform)



document.docx


Note: Template Revision History and Instructions for using this document can be found in

Hidden Text.

To display/hide hidden text:

File tab/ Options/Display/ "Hidden Text"

TABLE OF CONTENTS:

1 INTRODUCTION.............................................................................................5

1.1 PLANNING DOCUMENTATION......................................................................................5

1.2 OTHER DOCUMENTATION...........................................................................................6

2 SCOPE AND APPROACH.................................................................................7

2.1 SCOPE STATEMENT.....................................................................................................7

2.2 CRITICAL SUCCESS FACTORS......................................................................................7

2.3 DELIVERABLES............................................................................................................7

2.3.1 Project Deliverables and Acceptance....................................................................7

2.4 APPROACH..................................................................................................................7

3 REQUIREMENTS MANAGEMENT......................................................................8

3.1 TOOLS AND METHODS................................................................................................9

3.2 HIGH LEVEL REQUIREMENTS DEFINITION....................................................................9

3.3 DETAILED REQUIREMENTS..........................................................................................9

4 SCHEDULE MANAGEMENT.............................................................................9

4.1 SCHEDULE MANAGEMENT APPROACH........................................................................9

4.2 WORK BREAKDOWN STRUCTURE................................................................................9



document.docx


5 RISK MANAGEMENT....................................................................................11

5.1 RISK PROCESS..........................................................................................................11

5.2 TOOLS.......................................................................................................................11

5.3 RISK TOLERANCE THRESHOLDS................................................................................11

5.4 RISK RESPONSE PLANNING.......................................................................................12

5.5 RISK MEETINGS AND REPORTING..............................................................................12

5.6 ESCALATION.............................................................................................................12

6 MEASUREMENT PLAN..................................................................................12

7 REUSE PLAN...............................................................................................12

8 PROCUREMENT MANAGEMENT.....................................................................13

9 FINANCIAL MANAGEMENT APPROACH..........................................................14

9.1 BUDGET....................................................................................................................14

9.2 REVENUE..................................................................................................................14

9.3 COST AND REVENUE MONITORING AND CONTROL...................................................14

9.4 CHANGES TO COST OR REVENUE BASELINES...........................................................14

9.5 FINANCIAL MEASURES..............................................................................................14

10 QUALITY MANAGEMENT............................................................................15

10.1 QUALITY GOALS........................................................................................................15

10.2 QUALITY CONTROL....................................................................................................15

10.2.1 Work Product Reviews........................................................................................15

10.3 QUALITY ASSURANCE................................................................................................16

10.3.1 Quality Audits.....................................................................................................16

10.3.2 Other Reviews and Validations...........................................................................16

10.4 TESTING STRATEGY..................................................................................................16



document.docx


10.4.1 Testing Scope and Approach..............................................................................16

10.4.2 Testing Levels....................................................................................................16

10.4.3 Testing Monitoring and Control..........................................................................17

10.4.4 Client participation.............................................................................................17

11 CONFIGURATION MANAGEMENT................................................................18

11.1 BASELINE LIBRARIES.................................................................................................18

11.2 TOOLS AND METHODS..............................................................................................18

12 COMMUNICATION AND STAKEHOLDER MANAGEMENT.................................19

12.1 COMMUNICATIONS PLAN...........................................................................................19

12.2 ESCALATION PATH PROJECT ISSUES, RISKS, CHANGES.............................................19

12.3 CONTACT LIST..........................................................................................................20

12.4 STAKEHOLDER DEPENDENCIES.................................................................................20

13 TEAM MANAGEMENT.................................................................................21

13.1 ORGANISATION CHART.............................................................................................21

13.2 ROLES AND RESPONSIBILITIES..................................................................................21

13.3 STAFFING PLAN.........................................................................................................21

13.4 PROJECT TRAINING REQUIREMENTS..........................................................................21

14 CHANGE MANAGEMENT............................................................................22

14.1 CHANGE REQUEST PROCESS....................................................................................22

14.2 CHANGE CONTROL BOARD.......................................................................................22

14.3 TOOLS AND METHODS..............................................................................................23

14.4 CHANGE REQUESTS..................................................................................................23

15 ESTIMATES..............................................................................................24

16 PROJECT APPROVAL.................................................................................25



document.docx


16.1 AFFECTED GROUP COMMITMENT..............................................................................25

16.2 ORGANIZATIONAL COMMITMENT..............................................................................25

16.3 CLIENT / BUSINESS PARTNER AGREEMENT...............................................................25

16.4 PROJECT COMPLETION SIGN-OFF..............................................................................25

17 APPENDIX................................................................................................26

17.1 ABBREVIATIONS AND ACRONYMS.............................................................................26



document.docx


1 INTRODUCTION

This Project Management Plan defines the processes used to plan, monitor, adjust, and control the

interrelated activities to achieve the project defined objective.

This Project Management Plan supports the delivery of the commitments made in the Project

Statement of Work (SoW) document that Hewlett Packard, hereafter referred to as "HP", will provide to

Customer, hereafter referred to as "Customer Name", under the Project Agreement.

1.1 PLANNING DOCUMENTATION

The diagram below shows how the consolidated project plan relates to other planning documents

relevant to the project:

The table below indicates which planning components are included within this document or elsewhere:



document.docx


Component Included in this

document? (Y/N)

Or N/A

Location of standalone or supplementary components

(or reason for N/A)

Statement of Work N

Project Charter N

Scope

Approach Documentation

Requirements Management Plan

High Level Requirements

Detailed Requirements N

Requirements Traceability Matrix

N

Work Breakdown Structure

Risk Management Plan

High Level Risk Assessment

Schedule Management Plan

Project Schedule N e.g. MSP and/or PPMC@ES

Measurement Plan

Reuse Plan

Procurement Management Plan

Financial Management Approach

Quality Management Plan

Project Testing Strategy

Configuration Management Plan

Change Management Plan

Communications Management Plan

Stakeholder Analysis and Management Plan

N



document.docx


Component Included in this

document? (Y/N)

Or N/A

Location of standalone or supplementary components

(or reason for N/A)

Team Management Plan

Role and Responsibilities N

Estimate Documentation

Issues/ Assumptions/Risk log N e.g. PPMC@ES and/or DAIR

1.2 OTHER DOCUMENTATION

The table below lists other key project documentation:

Document Location



document.docx


2 SCOPE AND APPROACH

Scope Statement

Section Content

Project Description / Objectives

High-Level Deliverables

Affected Products, Services,

Operations, Organizations

Unaffected Products, Services,

Operations, Organizations

Project Benefits / Business

Measures (optional)

2.1 CRITICAL SUCCESS FACTORS

The following table describes factors or activities that are required to ensure the success of this

project.

ID Critical Success Factors

CSF01

CSF02

2.2 DELIVERABLES

2.2.1 PROJECT DELIVERABLES AND ACCEPTANCE

The following table sets out the Deliverables for the Project.



document.docx


ID Deliverable Acceptance Criteria Due Provided by

(HP, Client,

Vendor)

Client Approval Require

d Y/N

D01

D02

2.3 APPROACH

The following table summarizes the alternatives assessed to address the project objectives and

requirements.

ID Alternative Solution Description

A

B

C

The following table lists the solution criteria that will be used to evaluate each alternative. The relative

importance of each criterion may also be indicated in the table (e.g., value from 0 to 1, number from 1

to 5, or high, medium, and low indicator).

ID Solution Criteria Importance (optional)

1

2

3

4

5

6

The table below describes how the alternatives have been evaluated.



document.docx


ID Alternative Evaluation 1 2 3 4 5 6 Total

A0

B0

C0

Recommendation Rationale

3 REQUIREMENTS MANAGEMENT

All requirements will be formally documented, reviewed and approved and placed under formal change

management (in accordance with the Change and Configuration Management plans). Forward and

backwards traceability will be maintained between each requirement and all other related solution

components.

Reviews of requirements will be performed using Work Product criteria as described in the Quality

Plan.

The table below lists the key requirements components, the tools or documents where they will be

defined and the reviewers and approvers (by name or role) for each component. Detailed

Requirements and Requirements traceability are managed separately. Refer to the Planning

Documentation table (Section 1.1) for the location of the Roles and Responsibilities definition.

3.1 TOOLS AND METHODS

The table below describes the tools and methods that will be used for defining and managing

requirements:

Requirements Management Activity Methods /Tools

High Level Requirements Definition

Detailed Requirements Definition e.g. HP ALM@ES

Requirements Traceability e.g. Standalone Requirements Traceability Matrix

3.2 HIGH LEVEL REQUIREMENTS DEFINITION



document.docx


ID Description Acceptance Criteria

Source Type

HLR01

HL02

3.3 DETAILED REQUIREMENTS

Detailed Requirements are documented separately. Refer to the Planning Documentation table

(Section 1.1) for the location of the Roles and Responsibilities definition.

4 SCHEDULE MANAGEMENT

4.1 SCHEDULE MANAGEMENT APPROACH

4.2 WORK BREAKDOWN STRUCTURE


The table below describes the tools and methods that will be used for schedule management:

Schedule Management Activity Methods /Tools

Project Schedule e.g. MSP

Schedule analysis e.g. HP Schedule Quality Analyzer



document.docx


5 RISK MANAGEMENT

5.1 RISK PROCESS

The following diagram describes the standard HP Risk Process. This process will be used in accordance

with guidance in the HP Organizational Risk Management Plan.

5.2 TOOLS

The following tools/methods will be used to capture and manage risk

Risk Management Activity Risk management Output and Tools

High Level Risk Assessment

Risk Management Planning Project Plan

Risk Identification e.g. PPMC or DAIR

Risk Analysis

Risk Response Planning

Risk Monitoring and Control

Risk Cost Management e.g. E3T



document.docx


5.3 RISK TOLERANCE THRESHOLDS

The table below describes agreed Risk Tolerances by Risk Impact

Impact Time Quality Cost

Critical impact (red) > 2 weeks variance on plan

>5% variance on quality criteria

>$5K variance on plan

Significant impact (amber) > 1 weeks variance on plan

>2% variance on quality criteria

>$2K variance on plan

Minor impact (green) < 1 weeks variance on plan

<2% variance on quality criteria

<$2K variance on plan

5.4 RISK RESPONSE PLANNING

5.5 RISK MEETINGS AND REPORTING

Risk Meetings and Reporting are defined in the Communication Plan.

5.6 ESCALATION



document.docx


6 MEASUREMENT PLAN

Goal Measure(s) Source(s) Comments

On Time Date variance on Client agreed Milestones

Baselined schedule

Within Budget Cost variance (Cost EAC –Baseline cost/Baseline Cost )

Margin Erosion ((Revenue EAC – Cost EAC/Revenue EAC) – (Baseline Revenue-Baseline Cost/Baseline Revenue))

E3T /Compass

Scope Risks/Issues (# Open/# Closed)

Scope Change Requests

PPMC/DAIR

Quality Rework Effort

Defects

Supplier Performance

Audit and Review Non-Conformances

Compass

Work Product Reviews

Test Results

Supplier Evaluations

Post Milestone Project Review results

Audit and Project Review results

Client Satisfaction

Client satisfaction ratings

Client satisfaction survey

7 REUSE PLAN

The following table describes assets that will be reused by the project or made available by the project

for reuse.

Reuse Asset Consuming?Y / N

Harvesting?Y / N

Asset Type Reuse Repository



document.docx


Reuse Asset Consuming?Y / N

Harvesting?Y / N

Asset Type Reuse Repository

8 PROCUREMENT MANAGEMENT

The following table describes goods and services that must be procured to support the project:

Description Quantity Date Required by Duration



document.docx


9 FINANCIAL MANAGEMENT APPROACH

Budget

The budget will be the basis on which actual costs (expenses) are monitored.

The budget will be determined once estimation is complete and the estimates have been allocated out

across the life of the project. Once the cost estimate is approved, it will be baselined as the project

baselined budget.

The budget will be developed in native currency and when required for reporting converted to US

dollars (USD).

9.1 REVENUE

The Revenue is the income generated by activities. It refers to the money received from clients for HP

services or products.

Revenue will be calculated by cost plus management reserve (contingencies) and profit margin.

The project will track sold revenue against actual revenues received.

9.2 COST AND REVENUE MONITORING AND CONTROL

The following table lists the methods used for Cost and Revenue tracking:

Component/Activity Method/Tool

Baselined Financial Plan of Record (POR) The approved financial plan of record (POR) will be

loaded into COMPASS.

If project change controls are approved, these are

added to the original POR.

Reforecasting Monthly reforecasting will be performed via E3T

resulting in an updated Estimate to Complete

Governance Scorpio reporting will be used to monitor project

financial performance.

9.3 CHANGES TO COST OR REVENUE BASELINES

All changes to costs or revenue will be approved by formal change control. Approved financial

changes will be reflected in the financial figures (expenses and revenues) as the revised or current

baselines.



document.docx


9.4 FINANCIAL MEASURES

Refer to the Measurement Plan.



document.docx


10 QUALITY MANAGEMENT

Quality Goals

Measures aligned with the performance and quality goals will be collected and reported, as defined in

the Measurement Plan, to determine performance against these objectives.

The project will adhere to and support Performance and Quality goals and objectives and may

additionally support project and/or client specific quality goals and objectives.

Customer / Project Quality Goals Method used to achieve the goal

(e.g. zero post release defects) (E.g. Test driven development, continuous

integration, daily regression testing, formal reviews

of key components etc.)

Compliance to xxx standards

10.1 QUALITY CONTROL

Quality Control refers to quality related activities associated with the creation of project deliverables.

Quality control is used to verify that deliverables are of acceptable quality and that they are complete

and correct.

10.1.1WORK PRODUCT REVIEWS

Work Product Reviews are performed to ensure work products are free from defects and adhere to

Quality standards.

The reviews enable delivery of a quality product, and decrease project effort, cost and duration by

identifying defects early in the Project lifecycle phases.

The table below lists the work products that will be formally reviewed, additional criteria and standards

used to review (in addition to EDGE general and specific work-product criteria which will be used for all

work product reviews), the review method and the names or roles of the reviewers:

Work Products Reviewed

Other Criteria and Standards used

Review method

Participants Comments

Statement of Work Defect Removal Review

Business analysts

Developer

Tester

Project Plan (all components)

Verification Review

Peer Project



document.docx


Work Products Reviewed

Other Criteria and Standards used

Review method

Participants Comments

Manager

Project team members

SMEs

Requirements Documentation

Defect Removal Review

Peer Project Manager

Business analysts

Developer

Tester

10.2 QUALITY ASSURANCE

Quality Assurance addresses the processes used to create the deliverables. Examples of quality

assurance include process checklists, project audits and methodology and standards development.

10.2.1QUALITY AUDITS

The following table describes the audits that will be performed for the project:

Audit Point When Criteria used

Participants

e.g. Initiate Project After Project Plan approval

EDGE Initiate Project

Project Manager

QA SME

10.2.2OTHER REVIEWS AND VALIDATIONS

The following table describes other reviews and validations that will be performed for the project:

Review Type Reviewer(s) Criteria Timing

Project Healthcheck

PMO representative, Programme Mgr Critical projects Healthcheck

At end of Project planning

When requested by PMO leader



document.docx


Review Type Reviewer(s) Criteria Timing

Higher level management review

Account Delivery Mgr, Delivery Assurance Mgr, Technical / Architecture, Applications Delivery, Programme Mgr

High level Review Criteria

Technical Review

Technical / Architecture Regional Technical Review

Post Milestone Project Review

Project Manager

Project Team members

SMEs

EDGE PMPR During Project Execution

During Project Closedown

10.3 TESTING STRATEGY

10.3.1TESTING SCOPE AND APPROACH

10.3.2TESTING LEVELS

The following table describes the levels of testing that will be undertaken:

Test Level Prerequisites Entry/Exit criteria

Acceptance Criteria

e.g. Unit Testing

10.3.3TESTING MONITORING AND CONTROL

The approach to Testing Tracking and Reporting is defined via the Measurement and Communication

plans.

10.3.4CLIENT PARTICIPATION



document.docx


11 CONFIGURATION MANAGEMENT

Baseline Libraries

Baseline Contents Location / Tool

CCB

Planning Project Commitments

Statement of Work

Estimate Documentation

Schedule

e.g. Starteam / Sharepoint

Full

Requirements High level and detail level Requirements Full

Architecture Use Case, Logical, Physical, Development, Process Views.

Internal

Design Business Organisation Designs

Logical System Specifications

Physical Design

Application Interface / Process Specifications

Technical Architecture Specification

Internal

Integration Test Plans

Implementation Plan

Release Strategy

Internal

Product Application Software / Data e.g. Starteam Full


The following table describes the tools and methods that will be used to support Configuration

Management activities for this project:

Configuration Management Activity Methods Tools

Document Control e.g. Sharepoint

Software / data configuration control e.g. Starteam



document.docx


12 COMMUNICATION AND STAKEHOLDER MANAGEMENT

Communications Plan

The following table describes the communications approach for the project:

Communication item Description/Purpose Frequency Media Audience Responsible Distribution

Status Report Provide Client and HP Management an overview of project status including significant issues and risks

Fortnightly PPMC Portfolio Manager, Client Sponsor

Project Manager Audience plus EPO

Team Meeting Forum to plan and coordinate work required for project

Weekly Tele Conf HP Project Team

Project Manager Audience

Client Meeting Provide general progress update and requests for escalation

Weekly Tele Conf Client Project Manager


Vendor Meeting Provide general progress update and requests for escalation

Weekly Tele Conf Vendors

Project Manager


Account Governance Meeting

Review PPMC reports and escalate any issues outstanding

Weekly Tele Conf Account team

Project Manager

EPO Audience



document.docx


Communication item Description/Purpose Frequency Media Audience Responsible Distribution

Client Satisfaction Survey To review the client satisfaction on the project

At end of significant milestones – (at least art end of project)

Client Survey form

Client Sponsor Project Manager Audience

PMO

Project Team

Change Control Board Meeting

Review, evaluate, approve or reject, and prioritize change requests. Group approved change requests into releases

Fortnightly Tele Conf Change Control Board

Change Control Board (incl PM)

Audience

Project Team

12.1 ESCALATION PATH PROJECT ISSUES, RISKS, CHANGES

Sequenc

e

Role

1. Project Manager

2. Program Manager

3. Executive / Director

4.



document.docx


12.2 CONTACT LIST

The table below lists the contact details for key project stakeholders.

Name Company/Role Email Tel # Mobile #

12.3 STAKEHOLDER DEPENDENCIES

The following table describes the key dependencies pertaining to stakeholders:

Stakeholders Dependency description Required by (Date)

12.4 STAKEHOLDER ANALYSIS AND MANAGEMENT

Stakeholder Analysis and Management is documented separately. Refer to the Planning Documentation table.



document.docx


13 TEAM MANAGEMENT

Organisation Chart

13.1 ROLES AND RESPONSIBILITIES

Roles and Responsibilities are documented separately. Refer to the Planning Documentation table

(Section 1.1) for the location of the Roles and Responsibilities definition.

13.2 STAFFING PLAN

Units of Time Days/Weeks/Months

Role / Skill Set / Resource

1 2 3 4 5 6 7 8 9 10 11 12

Project Manager

Lead Technical

Business Analyst

Developer

Tester

Vendor

Customer

Total Staffing 1 2 3 4 5 6 7 8 9 10 11 12

13.3 PROJECT TRAINING REQUIREMENTS

Role Training Method Timing



document.docx


14 CHANGE MANAGEMENT

This section describes the approach to managing changes and controlling configuration items. Refer

also to the Roles and Responsibilities section for definitions and assignments of the roles involved.

14.1 CHANGE REQUEST PROCESS

14.2 CHANGE CONTROL BOARD

The Change Control Board (CCB) will review the impact of proposed changes to scope and other items

identified as requiring formal CM control. The CCB will approve, decline or defer Change Requests and

ensure that every baseline change is authorised and communicated to all stakeholders.

Any changes impacting scope, schedule or budget will be approved via the full CCB which will include

Client representation.

CCB Authority Members



document.docx


Full CCB Approves/Reject/Defer changes/ defect fixes, baselines and releases.

Project Manager

Client Project Manager

Programme Manager

Configuration Controller

Internal CCB Approves Change Requests that do not impact the project schedule, budget, scope.

Project Manager

Configuration Controller


The table below describes the tools/methods that will be used to manage project changes

Change Management Activity Methods Tools

Change Request Form e.g. email /CR form (link or reference CR Request)

Change Request log e.g. PPMC

14.4 CHANGE REQUESTS

Change Requests may be submitted via email. The request should include details of the requestor,

priority, description of change, details of the reason for requesting the change and any known issues,

risks, dependencies or assumptions associated with the change. The following form can be copied into

an email to facilitate the process:

Change Request

Client Reference No: Change Required by:

Client Project Manager: Date Request submitted:

Authorised Requestor Priority:

Change Details

Description of Change:

Benefit of/Reason for Change Request:

Issues/Concerns with Change Request:

Risks:

Assumptions:

Dependencies:



document.docx




document.docx


15 ESTIMATES

Historical Data

Data Type Name / Location Comment

Size Estimates

Product / Service Name

Components Unit of Measure

Modified Deleted Created Reused

Totals N/A 0 0 0 0

Effort Estimates

WBS Task Minimum Most Likely Maximum Estimate

Totals 0 0 0 0



document.docx


16 PROJECT APPROVAL

Affected Group Commitment

The following groups agree to the project commitments that affect them:

Group Name Date Authorised Name

Configuration Management SME

Metric SME

Process Management SME

Quality Assurance SME

16.1 ORGANIZATIONAL COMMITMENT

The following individuals approve the contents of this document:

Project Role Date Authorised Name

Project Manager

Leadership Team

16.2 CLIENT / BUSINESS PARTNER AGREEMENT

The following individuals approve the contents of this document and authorize HP to proceed with the

work described herein:



Client Leadership Team

16.3 PROJECT COMPLETION SIGN-OFF

The following individuals acknowledge that HP has completed the work described in this document:


Project Manager




document.docx


17 APPENDIX

17.1 ABBREVIATIONS AND ACRONYMS

Abbreviation/Acronym Definition



document.docx

Documents

consolidated_project_plan.docx