<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.Introduction5
1.1Purpose5
1.2Scope5
1.3Definitions, Acronyms and Abbreviations5
1.4References5
1.5Overview5
2.Project Overview6
2.1Project Name, Code and Leader6
2.2Project Purpose, Scope and Objectives6
2.3Assumptions and Constraints6
2.3.1Critical Assumptions and Constraints6
2.3.2Non-Critical Assumptions and Constraints6
2.4Project Milestones6
2.5Project Deliverables6
2.6Tailoring Guidelines6
2.7Software Development Life Cycle7
3.Project Organization8
3.1Organizational Structure8
3.2External Interfaces10
3.3Roles and Responsibilities10
3.3.1<Organizational Unit Name>10
4.Management Process11
4.1Work Breakdown Structure (WBS)11
4.2Project Estimates11
4.2.1Estimation Technique11
4.2.2Size11
4.2.3Effort11
4.3Project Schedule11
4.3.1Pre-Development Schedule11
4.3.2Development Schedule11
4.4Project Phases, Iterations and Releases11
4.4.1Project Phases11
4.4.2Project Iterations11
4.4.3Releases11
4.5Project Resourcing11
4.5.1Staffing11
4.5.2Resource Acquisition11
4.5.3Training12
4.6Project Budget12
4.7Project Monitoring and Control12
4.7.1Schedule Control12
4.7.2Budget Control12
4.7.3Measurements12
4.8Risk Management Plan12
4.9Project Closure12
5.Technical Process Plans13
5.1User Experience Design13
5.2Requirements Management13
5.3Analysis and Design13
5.4Development Plan13
5.5Peer Review Plan13
5.6Project Maintenance13
5.7Test Plan13
5.8Tools, Techniques and Standards13
5.8.1Tools13
5.8.2Techniques and Standards14
5.9Infrastructure14
5.10Facilities14
5.11Security Plan14
6.Supporting Process Plans15
6.1Configuration Management Plan15
6.2Documentation15
6.3Software Quality Assurance Plan15
6.4Intergroup Coordination15
6.5Communication15
6.6Problem Resolution15
6.7Subcontractor Management15
7.Additional plans16
8.Appendices16
Project Management Plan
[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.]
[Specify the purpose of this Project Management Plan.]
[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.]
[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.]
[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:
Document Title | Publishing Organization |
<Title> | <Organization Name> |
|
|
|
|
|
|
[This subsection should describe what the rest of the Project Management Plan contains and explain how the document is organized.]
[Specify the project name, project code and project leader (project manager).]
Project Name: <Project Name>
Project Code: <xxx-xxx>
Project Leader: <Name>
[A brief description of the purpose and objectives of this project, and a brief description of what deliverables the project is expected to deliver.]
[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.]
[State the critical assumptions and constraints affecting the project.]
[State the non-critical assumptions and constraints affecting the project.]
[Tabular list of major milestones to be achieved during the project, with target dates.]
Milestone | Target Achievement Date |
<Milestone Name> | <dd/mm/yyyy> |
|
|
|
|
|
|
[Tabular list of the artifacts to be created during the