Академический Документы
Профессиональный Документы
Культура Документы
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
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:
Saved 20-Feb-2015
HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724
Page 3 of 32
TABLE OF CONTENTS:
1
INTRODUCTION............................................................................................. 5
1.1
PLANNING DOCUMENTATION......................................................................................5
1.2
OTHER DOCUMENTATION............................................................................................ 6
SCOPE STATEMENT..................................................................................................... 7
2.2
2.3
DELIVERABLES............................................................................................................ 7
2.3.1
2.4
3
APPROACH.................................................................................................................. 7
REQUIREMENTS MANAGEMENT......................................................................8
3.1
3.2
3.3
DETAILED REQUIREMENTS.......................................................................................... 9
SCHEDULE MANAGEMENT.............................................................................9
4.1
4.2
RISK MANAGEMENT....................................................................................11
5.1
RISK PROCESS.......................................................................................................... 11
5.2
TOOLS....................................................................................................................... 11
5.3
5.4
5.5
Saved 20-Feb-2015
HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724
Page 4 of 32
5.6
ESCALATION.............................................................................................................. 12
MEASUREMENT PLAN..................................................................................12
REUSE PLAN............................................................................................... 12
PROCUREMENT MANAGEMENT.....................................................................13
BUDGET.................................................................................................................... 14
9.2
REVENUE.................................................................................................................. 14
9.3
9.4
9.5
FINANCIAL MEASURES.............................................................................................. 14
10
QUALITY MANAGEMENT............................................................................15
CONFIGURATION MANAGEMENT................................................................18
HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724
Page 5 of 32
TEAM MANAGEMENT.................................................................................21
CHANGE MANAGEMENT............................................................................22
ESTIMATES...............................................................................................24
16
PROJECT APPROVAL..................................................................................25
APPENDIX................................................................................................26
Saved 20-Feb-2015
HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724
Page 6 of 32
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
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
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
Estimate Documentation
Issues/ Assumptions/Risk log
1.2
OTHER DOCUMENTATION
Document
Saved 20-Feb-2015
Location
HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724
Page 8 of 32
Saved 20-Feb-2015
HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724
Page 9 of 32
SCOPE STATEMENT
Section
Content
High-Level Deliverables
Operations, Organizations
Unaffected Products, Services,
Operations, Organizations
Project Benefits / Business
Measures (optional)
1.4
The following table describes factors or activities that are required to ensure the success of this
project.
ID
CSF01
CSF02
1.5
DELIVERABLES
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
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
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
The table below describes the tools and methods that will be used for defining and managing
requirements:
Requirements Management Activity
Methods /Tools
e.g. HP ALM@ES
Requirements Traceability
1.8
ID
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
1.11
1.12
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
Methods /Tools
Project Schedule
e.g. MSP
Schedule analysis
Saved 20-Feb-2015
HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724
Page 13 of 32
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
Project Plan
e.g. PPMC or DAIR
Risk Analysis
Risk Response Planning
Risk Monitoring and Control
Risk Cost Management
1.15
e.g. E3T
Saved 20-Feb-2015
HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724
Page 14 of 32
Impact
Time
Quality
Cost
>5% variance on
quality criteria
>$5K variance
on plan
>2% variance on
quality criteria
>$2K variance
on plan
<2% variance on
quality criteria
<$2K variance
on plan
1.16
1.17
1.18
Saved 20-Feb-2015
ESCALATION
HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724
Page 15 of 32
MEASUREMENT PLAN
Goal
Measure(s)
Source(s)
On Time
Baselined schedule
Within Budget
E3T /Compass
Comments
Margin Erosion
((Revenue EAC Cost
EAC/Revenue EAC)
(Baseline RevenueBaseline Cost/Baseline
Revenue))
Scope
Risks/Issues (# Open/#
Closed)
PPMC/DAIR
Rework Effort
Compass
Defects
Supplier Performance
Test Results
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
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
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
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
Governance
1.22
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
HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724
Page 18 of 32
Saved 20-Feb-2015
HP Restricted
2014 Hewlett-Packard Development Company, L.P. All rights reserved.
284660724
Page 19 of 32
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)
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.
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
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
Criteria
used
EDGE
Initiate
Project
Participants
Project Manager
QA SME
Reviewer(s)
Criteria
Critical projects
Healthcheck
Timing
At end of Project
planning
When requested
by PMO leader
Higher level
management
review
Technical
Review
Technical / Architecture
Regional Technical
Review
Post Milestone
Project Review
Project Manager
EDGE PMPR
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
1.27
TESTING STRATEGY
10.1.5TESTING LEVELS
The following table describes the levels of testing that will be undertaken:
Test Level
Prerequisites
Entry/Exit
criteria
Acceptance Criteria
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
Full
Architecture
Internal
Design
Internal
Test Plans
Internal
Implementation Plan
Release Strategy
Product
1.29
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
e.g. Starteam
COMMUNICATIONS PLAN
The following table describes the communications approach for the project:
Communication item
Description/Purpose
Frequency
Media
Audience
Responsible
Distribution
Status Report
Fortnightly
PPMC
Portfolio
Manager,
Client Sponsor
Project Manager
Audience plus
EPO
Team Meeting
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
Weekly
EPO
Audience
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
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
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
Tel #
Mobile #
STAKEHOLDER DEPENDENCIES
Dependency description
Required by (Date)
1.34
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 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
10
11
12
Project Manager
Lead Technical
Business Analyst
Developer
Tester
Vendor
Customer
Total Staffing
1.38
Role
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
1.40
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
Project Manager
Configuration Controller
budget, scope.
1.41
The table below describes the tools/methods that will be used to manage project changes
Change Management Activity
Methods Tools
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:
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
The following groups agree to the project commitments that affect them:
Group Name
Date
Authorised Name
1.44
ORGANIZATIONAL COMMITMENT
Date
Authorised Name
Project Manager
Leadership Team
1.45
The following individuals approve the contents of this document and authorize HP to proceed with the
work described herein:
Project Role
Date
Authorised Name
1.46
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