(项目管理)项目管理计划模板(英文)

Project Management Plan

Version [Note: The following template is provided for use in Xavor projects. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document.]

Revision History

[For every revision of this document, provide the revision history that should include the date of revision, version number, description of the changes in the document, and author of the document for that particular version.]

Distribution List

[State the persons/teams/groups to whom this document should be distributed whenever the document is revised. Also state the name of their parent organization.]

Table of Contents

1.Introduction 5

1.1Purpose 5

1.2Scope 5

1.3Definitions, Acronyms and Abbreviations 5

1.4References 5

1.5Overview 5

2.Project Overview 6

2.1Project Name, Code and Leader 6

2.2Project Purpose, Scope and Objectives 6

2.3Assumptions and Constraints 6

2.3.1Critical Assumptions and Constraints 6

2.3.2Non-Critical Assumptions and Constraints 6

2.4Project Milestones 6

2.5Project Deliverables 6

2.6Tailoring Guidelines 7

2.7Software Development Life Cycle 7

3.Project Organization 8

3.1Organizational Structure 8

3.2External Interfaces 10

3.3Roles and Responsibilities 10

3.3.1 10

4.Management Process 11

4.1Work Breakdown Structure (WBS) 11

4.2Project Estimates 11

4.2.1Estimation Technique 11

4.2.2Size 11

4.2.3Effort 11

4.3Project Schedule 11

4.3.1Pre-Development Schedule 11

4.3.2Development Schedule 11

4.4Project Phases, Iterations and Releases 11

4.4.1Project Phases 11

4.4.2Project Iterations 11

4.4.3Releases 11

4.5Project Resourcing 11

4.5.1Staffing 11

4.5.2Resource Acquisition 12

4.5.3Training 12

4.6Project Budget 12

4.7Project Monitoring and Control 12

4.7.1Schedule Control 12

4.7.2Budget Control 12

4.7.3Measurements 12

4.8Risk Management Plan 12

4.9Project Closure 12

5.Technical Process Plans 13

5.1User Experience Design 13

5.2Requirements Management 13

5.3Analysis and Design 13

5.4Development Plan 13

5.5Peer Review Plan 13

5.6Project Maintenance 13

5.7Test Plan 13

5.8Tools, Techniques and Standards 13

5.8.1Tools 13

5.8.2Techniques and Standards 14

5.9Infrastructure 14

5.10Facilities 14

5.11Security Plan 14

6.Supporting Process Plans 15

6.1Configuration Management Plan 15

6.2Documentation 15

6.3Software Quality Assurance Plan 15

6.4Intergroup Coordination 15

6.5Communication 15

6.6Problem Resolution 15

6.7Subcontractor Management 15

7.Additional plans 16

8.Appendices 16

Project Management Plan

1. Introduction

[The introduction of the Project Management Plan should provide an overview of the entire

document. It should include the purpose, scope, definitions, acronyms, abbreviations, references and overview of this Project Management Plan.]

1.1 Purpose

[Specify the purpose of this Project Management Plan.]

1.2 Scope

[A brief description of the scope of this Project Management Plan; what Project(s) it is

associated with, and anything else that is affected or influenced by this document.]

1.3 Definitions, Acronyms and Abbreviations

[This subsection should provide the definitions of all terms, acronyms, and abbreviations

required to interpret properly the Project Management Plan. This information may be provided by reference to the project Glossary.]

1.4 References

[This subsection should provide a complete list of all documents referenced elsewhere in the

Project Management Plan. Each document should be identified by title, report number (if

applicable), date, and publishing organization. Specify the sources from which the references

can be obtained. This information may be provided by reference to an appendix or to another

document. For the Project Management Plan, the list of referenced artifacts may include:

?Risk Management Plan

?User Interfaces Guidelines

?Configuration Management Plan

?Software Quality Assurance Plan, etc.]

1.5 Overview

[This subsection should describe what the rest of the Project Management Plan contains and

explain how the document is organized.]

2. Project Overview

2.1 Project Name, Code and Leader

[Specify the project name, project code and project leader (project manager).]

Project Name:

Project Code:

Project Leader:

2.2 Project Purpose, Scope and Objectives

[A brief description of the purpose and objectives of this project, and a brief description of what

deliverables the project is expected to deliver.]

2.3 Assumptions and Constraints

[A list of assumptions that this plan is based on, and any constraints (e.g. budget, staff, equipment,

schedule, etc.) that apply to the project. Make a distinction between critical and non-critical

factors.]

2.3.1 Critical Assumptions and Constraints

[State the critical assumptions and constraints affecting the project.]

2.3.2 Non-Critical Assumptions and Constraints

[State the non-critical assumptions and constraints affecting the project.]

2.4 Project Milestones

[Tabular list of major milestones to be achieved during the project, with target dates.]

2.5 Project Deliverables

[Tabular list of the artifacts to be created during the project, with target delivery dates.]

2.6 Tailoring Guidelines

[Specify the tailoring guidelines for the project.]

2.7 Software Development Life Cycle

[Specify the Software Development Life Cycle that is to be followed in the project.]

3. Project Organization

3.1 Organizational Structure

[Describe the organizational structure of the project team, including management and other

review authorities. This should include identification of all project organizational units and a

description of their function and responsibility. A diagram of the organizational structure should also be attached for further illustration.

Examples of project organizational units are:

?Project Implementation Committee

?Project Steering Committee

?Project Management Team

?Architecture Group

?User Experience Design Team

?Requirements Team

?Analysis and Design Team

?Implementation Group

?Development Team

?Database Management Team

?Testing Team

?Infrastructure Team

?Configuration Management Team

?Software Quality Assurance Team, etc.]

3.2 External Interfaces

[Describe how the project interfaces with external groups. For each external group, identify the internal/external contact names.]

3.3 Roles and Responsibilities

[Specify the roles, responsibilities and role holders within each organizational unit of the project.] 3.3.1

4. Management Process

4.1 Work Breakdown Structure (WBS)

[List the activities necessary for completing the project.]

4.2 Project Estimates

4.2.1 Estimation Technique

[Specify the estimation method and the reason for its choice. Provide the estimated cost as well as the basis for those estimates, and the points/circumstances in the project when re-estimation will occur.]

4.2.2 Size

[State the size of each activity as calculated according to the estimation technique. Units of size may be in LOC, FP, etc.]

4.2.3 Effort

[Specify the amount of effort required to perform each activity on the basis of the size estimation.

Units may be man-hours, man-days, etc.]

4.3 Project Schedule

[Diagrams/tables showing target dates for completion of iterations and phases, release points,

demos, and other milestones. Critical path must be specified. Usually enclosed by reference to MS Project file.]

4.3.1 Pre-Development Schedule

[This schedule will cater for project planning, requirements, analysis and design activities.]

4.3.2 Development Schedule

[This schedule will cater coding, testing and deployment activities.]

4.4 Project Phases, Iterations and Releases

4.4.1 Project Phases

[Identify phases and major milestones with their achievement criteria.]

4.4.2 Project Iterations

[Specify the number of iterations and list the objectives to be accomplished for each of the

iterations.]

4.4.3 Releases

[Brief descriptions of each software release, whether demo, beta, etc.]

4.5 Project Resourcing

4.5.1 Staffing

[Identify here the numbers and type of staff required (including and special skills or experience), scheduled by project phase or iteration. State what resources are critical.]

4.5.2 Resource Acquisition

[Describe how you will approach finding and acquiring the staff needed for the project.]

4.5.3 Training

[List any special training project team members will require, with target dates for when this

training should be completed.]

4.6 Project Budget

[Allocation of costs against the WBS and the project phases.]

4.7 Project Monitoring and Control

4.7.1 Schedule Control

[Describes the approach to be taken to monitor progress against the planned schedule and how to take corrective action when required.]

4.7.2 Budget Control

[Describes the approach to be taken to monitor spending against the project budget and how to take corrective action when required.]

4.7.3 Measurements

[Describe the types of measurements to be taken, their frequency, and responsible

workers/entities for this purpose.]

4.8 Risk Management Plan

[Enclosed by reference]

4.9 Project Closure

[Describe the activities for the orderly completion of the project, including staff reassignment, archiving of project materials, post-mortem debriefings and reports etc.]

5. Technical Process Plans

5.1 User Experience Design

[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]

5.2 Requirements

[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]

5.3 Analysis and Design

[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]

5.4 Development Plan

[Enclosed by reference]

5.5 Peer Review Plan

[Specify the work products to be peer reviewed, type of peer review, their frequency, etc.]

5.6 Maintenance

[Describe details of any software maintenance for the warranty period of the project.]

5.7 Test Plan

[Enclosed by reference]

5.8 Tools, Techniques and Standards

5.8.1 Tools

5.8.1.1 Project Management Tools

[Specify the project management tools that are to be used in the project and the reasons for their selection. Examples of areas to be covered are project planning, project scheduling, project

monitoring, status reporting, measurements, etc. Examples of these tools are MS Project, etc.]

5.8.1.2 Requirements Management Tools

[Specify the requirements management tools that are to be used in the project and the reasons for their selection. Examples of areas to be covered are requirements gathering, requirement issue

resolution, requirement change management, measurements, etc. Examples of these tools are

Rational Requisite Pro, EINS, etc.]

5.8.1.3 System Analysis & Design Tools

[Specify the system analysis and design tools that are to be used in the project and the reasons

for their selection. Examples of tools in this area are Visio, Rational Rose, Power Designer etc.]

5.8.1.4 Languages

[Specify the languages that are to be used for software development in the project and the

reasons for their selection. Examples of languages are HTML, Java, etc.]

5.8.1.5 User-Interface Development Tools

[Specify the tools that are to be used for UI development in the project and the reasons for their selection. Examples of these tools can be Dreamweaver, Flash, etc.]

5.8.1.6 Database Management System Software

[Specify the database management system software that is to be used in the project and the

reasons for their selection. Examples of these tools are Oracle, SQL Server, etc.]

5.8.1.7 Third Party Software

[Specify any third party software that is to be used in the project and the reasons for their

selection. Examples are Inktomi, Infranet, etc.]

5.8.1.8 Software Testing Tools

[Specify the software testing tools that are to be used in the project and the reasons for their

selection. Examples of these tools are WinRunner, LoadRunner, etc.]

5.8.1.9 Defect and Change Management Tools

[Specify the defect and change management tools that are to be used in the project and the

reasons for their selection. Examples of these tools are ClearQuest, etc.]

5.8.1.10 Configuration Management Tools

[Specify the configuration management tools that are to be used in the project and the reasons

for their selection. Examples of these tools are ClearCase, etc.]

5.8.1.11 Integrated Development Environment

[Specify the operating systems (platforms), web servers, application servers, development servers that are to be used in the project and the reasons for their selection. Examples of these tools are Sun Solaris, iPlanet, JBuilder, WebSphere, etc.]

5.8.2 Techniques and Standards

[Lists the documented project technical standards etc by reference. Examples may be:

User-Interface Guidelines

Programming Guidelines

Test Guidelines, etc.]

5.9 Infrastructure

[Specify hardware, network connectivity, bandwidth, etc., required in this project. Make a clear distinction about what factors are critical.]

5.10 Facilities

[Describe the facilities required for the execution of the project. This will cover physical

workspace, buildings, etc.]

5.11 Security Plan

[List down the security consideration e.g. of security can be operating system, access controls to site/product, physical security considerations.]

6. Supporting Process Plans

6.1 Configuration Management Plan

[Enclosed by reference]

6.2 Documentation

[Specify the documents that will be produced in the project, what document templates will be

used, and any other information pertaining to documentation.]

6.3 Software Quality Assurance Plan

[Enclosed by reference]

6.4 Intergroup Coordination

[Describe how different project groups will communicate with one another; specify dependencies, and commitments.]

6.5 Communication

[Specify how various workers/units/entities, both within and outside the project team, will

communicate with each other.]

6.6 Problem Resolution

[Describe the approach for resolving issues in the project, escalation procedures, etc.]

6.7 Subcontractor Management

[If subcontractors are involved in the project give details of what kind of contractors are required for various tasks, the duration for which they are required and how they will be managed.]

7. Additional plans

[Additional plans if required by contract or regulations.] 8. Appendices

[Attach any supplementary information.]