Вы находитесь на странице: 1из 32

Hewlett-Packard Development Company, LP.

Project Management Plan


Project Name
HP Restricted

Consolidated Project Management Plan

Customer Name
Prepared By: Name/Organization

Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 2 of 32

Consolidated Project Management Plan

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)

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"

Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 3 of 32

Consolidated Project Management Plan

TABLE OF CONTENTS:
1

INTRODUCTION............................................................................................. 5
1.1

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

1.2

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

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


2.1

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

2.2

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

2.3

DELIVERABLES............................................................................................................ 7

2.3.1
2.4
3

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

APPROACH.................................................................................................................. 7

REQUIREMENTS MANAGEMENT......................................................................8
3.1

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

3.2

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

3.3

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

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

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

4.2

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

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

Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 4 of 32

Consolidated Project Management Plan

5.6

ESCALATION.............................................................................................................. 12

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

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

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

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
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


Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 5 of 32

Consolidated Project Management Plan

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

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

Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 6 of 32

Consolidated Project Management Plan

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:

Component

Included in
this
document?
(Y/N)

Location of standalone or
supplementary components
(or reason for N/A)

Or N/A
Statement of Work

Project Charter

Scope
Approach Documentation
Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 7 of 32

Consolidated Project Management Plan

Component

Included in
this
document?
(Y/N)

Location of standalone or
supplementary components
(or reason for N/A)

Or N/A
Requirements Management Plan
High Level Requirements
Detailed Requirements

Requirements Traceability
Matrix

Work Breakdown Structure


Risk Management Plan
High Level Risk Assessment
Schedule Management Plan
Project Schedule

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

Team Management Plan


Role and Responsibilities

Estimate Documentation
Issues/ Assumptions/Risk log

1.2

e.g. PPMC@ES and/or DAIR

OTHER DOCUMENTATION

The table below lists other key project documentation:

Document

Saved 20-Feb-2015

Location

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 8 of 32

Consolidated Project Management Plan

Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 9 of 32

Consolidated Project Management Plan

SCOPE AND APPROACH


1.3

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)

1.4

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

1.5

DELIVERABLES

2.1.1 PROJECT DELIVERABLES AND ACCEPTANCE


The following table sets out the Deliverables for the Project.
ID

Deliverable

Acceptance Criteria

Due

Provided
by
(HP, Client,
Vendor)

Client
Approval
Require
d Y/N

D01
D02

1.6
Saved 20-Feb-2015

APPROACH
HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 10 of 32

Consolidated Project Management Plan

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.
ID

Alternative Evaluation

Total
0

Recommendation

Rationale

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.
Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 11 of 32

Consolidated Project Management Plan

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.

1.7

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

1.8
ID

HIGH LEVEL REQUIREMENTS DEFINITION


Description

Acceptance
Criteria

Source

Type

HLR0
1
HL02

1.9

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.

SCHEDULE MANAGEMENT
1.10

SCHEDULE MANAGEMENT APPROACH

1.11

WORK BREAKDOWN STRUCTURE

1.12

TOOLS AND METHODS

The table below describes the tools and methods that will be used for schedule management:
Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 12 of 32

Consolidated Project Management Plan

Schedule Management Activity

Methods /Tools

Project Schedule

e.g. MSP

Schedule analysis

e.g. HP Schedule Quality Analyzer

Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 13 of 32

Consolidated Project Management Plan

RISK MANAGEMENT
1.13

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.

1.14

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
Risk Identification

Project Plan
e.g. PPMC or DAIR

Risk Analysis
Risk Response Planning
Risk Monitoring and Control
Risk Cost Management

1.15

e.g. E3T

RISK TOLERANCE THRESHOLDS

The table below describes agreed Risk Tolerances by Risk Impact

Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 14 of 32

Consolidated Project Management Plan

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

1.16

RISK RESPONSE PLANNING

1.17

RISK MEETINGS AND REPORTING

Risk Meetings and Reporting are defined in the Communication Plan.

1.18

Saved 20-Feb-2015

ESCALATION

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 15 of 32

Consolidated Project Management Plan

MEASUREMENT PLAN
Goal

Measure(s)

Source(s)

On Time

Date variance on Client


agreed Milestones

Baselined schedule

Within Budget

Cost variance (Cost EAC


Baseline cost/Baseline
Cost )

E3T /Compass

Comments

Margin Erosion
((Revenue EAC Cost
EAC/Revenue EAC)
(Baseline RevenueBaseline Cost/Baseline
Revenue))
Scope

Risks/Issues (# Open/#
Closed)

PPMC/DAIR

Scope Change Requests


Quality

Rework Effort

Compass

Defects

Work Product Reviews

Supplier Performance

Test Results

Audit and Review NonConformances

Supplier Evaluations
Post Milestone Project
Review results
Audit and Project
Review results

Client
Satisfaction

Client satisfaction
ratings

Client satisfaction
survey

REUSE PLAN

The following table describes assets that will be reused by the project or made available by the project
for reuse.
Reuse Asset

Consumin
g?
Y/N

Harvestin
g?
Y/N

Asset Type

Reuse
Repository

PROCUREMENT MANAGEMENT

The following table describes goods and services that must be procured to support the project:
Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 16 of 32

Consolidated Project Management Plan

Description

Saved 20-Feb-2015

Quantity

Date Required by

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Duration

Page 17 of 32

Consolidated Project Management Plan

FINANCIAL MANAGEMENT APPROACH


1.19

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).

1.20

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.

1.21
CONTROL

COST AND REVENUE MONITORING AND

The following table lists the methods used for Cost and Revenue tracking:
Component/Activity
Baselined Financial Plan of Record (POR)

Method/Tool
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.

1.22

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.

1.23

FINANCIAL MEASURES

Refer to the Measurement Plan.


Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 18 of 32

Consolidated Project Management Plan

Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 19 of 32

Consolidated Project Management Plan

10 QUALITY MANAGEMENT
1.24

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
(e.g. zero post release defects)

Method used to achieve the goal


(E.g. Test driven development, continuous
integration, daily regression testing, formal reviews
of key components etc.)

Compliance to xxx standards

1.25

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
Statement of Work

Project Plan (all


components)

Other Criteria
and Standards
used

Review
method

Participants

Defect
Removal
Review

Business analysts

Verification
Review

Peer Project
Manager

Comments

Developer
Tester

Project team
members
SMEs
Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 20 of 32

Consolidated Project Management Plan

Work Products
Reviewed

Other Criteria
and Standards
used

Requirements
Documentation

Review
method
Defect
Removal
Review

Participants

Comments

Peer Project
Manager
Business analysts
Developer
Tester

1.26

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.1.2QUALITY AUDITS
The following table describes the audits that will be performed for the project:
Audit Point

When

e.g. Initiate Project

After Project Plan


approval

Criteria
used
EDGE
Initiate
Project

Participants
Project Manager
QA SME

10.1.3OTHER REVIEWS AND VALIDATIONS


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

Reviewer(s)

Criteria

PMO representative, Programme Mgr

Critical projects
Healthcheck

Timing
At end of Project
planning
When requested
by PMO leader

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

EDGE PMPR

Project Team members

During Project
Closedown

SMEs

Saved 20-Feb-2015

During Project
Execution

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 21 of 32

Consolidated Project Management Plan

1.27

TESTING STRATEGY

10.1.4TESTING SCOPE AND APPROACH

10.1.5TESTING 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.1.6TESTING MONITORING AND CONTROL


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

10.1.7CLIENT PARTICIPATION

Saved 20-Feb-2015

HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724

Page 22 of 32

11 CONFIGURATION MANAGEMENT
1.28

BASELINE LIBRARIES

Baseline
Planning

Contents

Location /
Tool

Project Commitments

e.g.
Starteam /
Sharepoint

Statement of Work
Estimate Documentation

CCB
Full

Schedule
Requirements

High level and detail level Requirements

Full

Architecture

Use Case, Logical, Physical, Development,


Process Views.

Internal

Design

Business Organisation Designs

Internal

Logical System Specifications


Physical Design
Application Interface / Process
Specifications
Technical Architecture Specification
Integration

Test Plans

Internal

Implementation Plan
Release Strategy
Product

Application Software / Data

1.29

e.g. Starteam

Full

TOOLS AND METHODS

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

12 COMMUNICATION AND STAKEHOLDER MANAGEMENT


1.30

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

Project Manager

Audience

Vendor Meeting

Provide general
progress update and
requests for escalation

Weekly

Tele Conf

Vendors

Project Manager

Audience

Account Governance
Meeting

Review PPMC reports


and escalate any issues
outstanding

Weekly

EPO

Audience

Client Satisfaction Survey

To review the client


satisfaction on the
project

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

Project Manager

Audience

Project
Manager
Tele Conf

Account team
Project
Manager

Client
Survey
form

Client Sponsor

PMO
Project Team

Communication item

Description/Purpose

Frequency

Media

Audience

Responsible

Distribution

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

1.31
Sequenc

Project Team

ESCALATION PATH PROJECT ISSUES, RISKS, CHANGES


Role

e
1.

Project Manager

2.

Program Manager

3.

Executive / Director

4.

1.32

CONTACT LIST

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

Company/Role

1.33

Email

Tel #

Mobile #

STAKEHOLDER DEPENDENCIES

The following table describes the key dependencies pertaining to stakeholders:


Stakeholders

Dependency description

Required by (Date)

1.34

STAKEHOLDER ANALYSIS AND MANAGEMENT

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

13 TEAM MANAGEMENT
1.35

ORGANISATION CHART

1.36

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.

1.37

STAFFING PLAN

Units of Time

Days/Weeks/Months

Role / Skill Set /


Resource

10

11

12

Project Manager
Lead Technical
Business Analyst
Developer
Tester
Vendor
Customer
Total Staffing

1.38
Role

PROJECT TRAINING REQUIREMENTS


Training

Method

Timing

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.

1.39

CHANGE REQUEST PROCESS

1.40

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
Full CCB

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

Members
Project Manager
Client Project Manager
Programme Manager
Configuration Controller

Internal CCB

Approves Change Requests that do


not impact the project schedule,

Project Manager
Configuration Controller

budget, scope.

1.41

TOOLS AND METHODS

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

1.42

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:

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

Effort Estimates
WBS Task

Minimum

Most Likely

Maximum

Estimate

Totals

16 PROJECT APPROVAL
1.43

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

1.44

ORGANIZATIONAL COMMITMENT

The following individuals approve the contents of this document:


Project Role

Date

Authorised Name

Project Manager
Leadership Team

1.45

CLIENT / BUSINESS PARTNER AGREEMENT

The following individuals approve the contents of this document and authorize HP to proceed with the
work described herein:
Project Role

Date

Authorised Name

Client Project Manager


Client Leadership Team

1.46

PROJECT COMPLETION SIGN-OFF

The following individuals acknowledge that HP has completed the work described in this document:
Project Role
Project Manager
Client Project Manager

Date

Authorised Name

17 APPENDIX
1.47
Abbreviation/Acronym

ABBREVIATIONS AND ACRONYMS


Definition

Вам также может понравиться