Professional Documents
Culture Documents
<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.]
Document #: Ver.:
Organization Level Template
XVR.0002/PMP 0
CMM – Xavor Corporation
Title: Page #:
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>
Title: Page #:
Table of Contents
1. Introduction 5
1.1 Purpose 5
1.2 Scope 5
1.3 Definitions, Acronyms and Abbreviations 5
1.4 References 5
1.5 Overview 5
2. Project Overview 6
2.1 Project Name, Code and Leader 6
2.2 Project Purpose, Scope and Objectives 6
2.3 Assumptions and Constraints 6
2.3.1 Critical Assumptions and Constraints 6
2.3.2 Non-Critical Assumptions and Constraints 6
2.4 Project Milestones 6
2.5 Project Deliverables 6
2.6 Tailoring Guidelines 6
2.7 Software Development Life Cycle 7
3. Project Organization 8
3.1 Organizational Structure 8
3.2 External Interfaces 10
3.3 Roles and Responsibilities 10
3.3.1 <Organizational Unit Name> 10
4. Management Process 11
4.1 Work Breakdown Structure (WBS) 11
4.2 Project Estimates 11
4.2.1 Estimation Technique 11
4.2.2 Size 11
4.2.3 Effort 11
4.3 Project Schedule 11
4.3.1 Pre-Development Schedule 11
4.3.2 Development Schedule 11
4.4 Project Phases, Iterations and Releases 11
4.4.1 Project Phases 11
4.4.2 Project Iterations 11
4.4.3 Releases 11
4.5 Project Resourcing 11
4.5.1 Staffing 11
4.5.2 Resource Acquisition 11
4.5.3 Training 12
4.6 Project Budget 12
Title: Page #:
7. Additional plans 16
8. Appendices 16
Title: Page #:
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.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.]
Title: Page #:
1.5 Overview
[This subsection should describe what the rest of the Project Management Plan contains and explain how
the document is organized.]
Title: Page #:
2. Project Overview
2.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>
Title: Page #:
Title: Page #:
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.]
Organizational Unit Description
<Organizational Unit Name> <Description>
Title: Page #:
Project Team
<Project Name>
Version: <x.x>
Date: <dd/mm/yyyy>
Project
Project Manager Management
Team
Software
User Experience
Development
Team
Team
System Database
Architecture Management
Team Team
Requirements
Testing Team
Team
Title: Page #:
Title: Page #:
4. Management Process
4.1 Work Breakdown Structure (WBS)
[List the activities necessary for completing the project.]
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.4.3 Releases
[Brief descriptions of each software release, whether demo, beta, etc.]
Title: Page #:
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.3 Training
[List any special training project team members will require, with target dates for when this training
should be completed.]
4.7.3 Measurements
[Describe the types of measurements to be taken, their frequency, and responsible workers/entities for this
purpose.]
Title: Page #:
5.2 Requirements
[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be
followed.]
5.6 Maintenance
[Describe details of any software maintenance for the warranty period of the project.]
5.8.1 Tools
Title: Page #:
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.]
Title: Page #:
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.]
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.5 Communication
[Specify how various workers/units/entities, both within and outside the project team, will communicate
with each other.]
Title: Page #:
7. Additional plans
[Additional plans if required by contract or regulations.]
8. Appendices
[Attach any supplementary information.]