<Project Name>

Project Management Plan

Version <x.x>

[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.]

Date	Version	Description	Author
<dd/mm/yyyy>	<x.x>	<Details>	<Name>

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

Document Recipient	Organization
<Role Name>	<Organization Name>

Table of Contents

1. Introduction

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

[Specify the purpose of this Project Management Plan.]

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

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

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

Document Title	Publishing Organization
<Title>	<Organization Name>

1. Overview

[This subsection should describe what the rest of the Project Management Plan contains and explain how the document is organized.]

2. Project Overview

1. Project Name, Code and Leader

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

Project Name: <Project Name>

Project Code: <xxx-xxx>

Project Leader: <Name>

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

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

1. Critical Assumptions and Constraints

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

2. Non-Critical Assumptions and Constraints

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

4. Project Milestones

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

Milestone	Target Achievement Date
<Milestone Name>	<dd/mm/yyyy>

5. Project Deliverables

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

Deliverables	Target Delivery Date
<Deliverable Name>	<dd/mm/yyyy>

6. Tailoring Guidelines

[Specify the tailoring guidelines for the project.]

7. Software Development Life Cycle

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

3. Project Organization

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

Organizational Unit	Description
<Organizational Unit Name>	<Description>




1. External Interfaces

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

External Organization	External Role	External Role Holder	Responsibility of External Role Holder	Internal Contact Role and Person
<Organization Name>	<Role Name>	<Role Holder Name>	<Responsibility Details>	<Role Name>, <Person Name>

2. Roles and Responsibilities

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

1. <Organizational Unit Name>

Role	Responsibility	Role Holder
<Role Name>	<Responsibility Detail>	<Role Holder Name>

4. Management Process

1. Work Breakdown Structure (WBS)

[List the activities necessary for completing the project.]

2. Project Estimates

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

2. Size

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

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

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

1. Pre-Development Schedule

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

2. Development Schedule

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

4. Project Phases, Iterations and Releases

1. Project Phases

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

2. Project Iterations

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

3. Releases

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

5. Project Resourcing

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

2. Resource Acquisition

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

3. Training

[List any special training project team members will require, with target dates for when this training should be completed.]

6. Project Budget

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

7. Project Monitoring and Control

1. Schedule Control

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

2. Budget Control

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

3. Measurements

[Describe the types of measurements to be taken, their frequency, and responsible workers/entities for this purpose.]

8. Risk Management Plan

[Enclosed by reference]

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

1. User Experience Design

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

2. Requirements

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

3. Analysis and Design

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

4. Development Plan

[Enclosed by reference]

5. Peer Review Plan

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

6. Maintenance

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

7. Test Plan

[Enclosed by reference]

8. Tools, Techniques and Standards

1. Tools

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

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

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

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

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

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

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

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

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

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

2. Techniques and Standards

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

User-Interface Guidelines

Programming Guidelines

Test Guidelines, etc.]

9. Infrastructure

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

10. Facilities

[Describe the facilities required for the execution of the project. This will cover physical workspace, buildings, etc.]

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

1. Configuration Management Plan

[Enclosed by reference]

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

3. Software Quality Assurance Plan

[Enclosed by reference]

4. Intergroup Coordination

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

5. Communication

[Specify how various workers/units/entities, both within and outside the project team, will communicate with each other.]

6. Problem Resolution

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

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

Xavor Corporation

	Organization Level Template CMM - Xavor Corporation	Document #: XVR.0002/PMP	Ver.: 0
Title: Project Management Plan			Page #: 2 of 17

Confidential

©Xavor Corporation, 2001

Page 2 of 17

---