Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.
Table of Contents
Section 1. Project Management Plan Introduction. 6
1.1. Version History and Sign-off 6
3.1. Project Scope Statement 9
3.1.2. Project Scope Boundaries. 9
3.2. Work Breakdown Structure. 9
3.4. Key Project Assumptions. 10
3.5. Key Project Constraints. 10
3.6. Key Project Dependencies. 11
3.7. Project Success Criteria. 11
3.8. Project Scope Management Approach. 11
3.8.1. Scope Management Processes 11
3.8.2. Scope Management Standards & Procedures. 11
3.8.3. Scope Management Methods, Tools & Techniques. 11
4. SCHEDULE MANAGEMENT PLAN. 12
4.1. Project Schedule Approach. 12
4.1.2. Estimate Level of Effort 12
4.1.3. Resource Allocation. 12
4.1.4. High-Level Timescale. 12
4.1.5. Determining Schedule Changes. 13
4.1.6. Obtaining Agreement on Schedule Changes. 13
4.1.7. Managing Schedule Changes. 13
4.1.8. Measuring & Reporting Schedule Performance. 13
4.2. Project Schedule Management 13
4.2.1. Schedule Management Processes. 13
4.2.2. Schedule Management Standards & Procedures. 13
4.2.3. Schedule Management Methods, Tools & Techniques. 14
6. Project Cost Management Approach. 15
6.1.2. Cost Status Reporting. 15
6.2. Project Cost Management 15
6.2.1. Roles & Responsibilities 15
6.2.2. Cost Management Processes. 16
6.2.3. Cost Management Standards & Procedures. 16
6.3. Cost Management Methods, Tools & Techniques. 16
7. QUALITY MANAGEMENT PLAN. 17
7.1. Quality Management Approach. 17
7.1.2. Define Project Quality. 17
7.1.3. Measure Project Quality. 17
7.2. Quality Assurance & Quality Control 17
7.2.1. Assessments, Reviews & Audits. 17
7.2.2. Improve Project Quality. 18
7.2.3. Quality Monitoring and Control 18
7.4. Project Quality Management 18
7.4.1.1. Roles and Responsibilities. 18
7.4.1.2. Quality Management Processes. 18
7.4.2. Quality Management Standards & Procedures 19
7.4.3. Quality Management Methods, Tools & Techniques. 19
8. HUMAN RESOURCES MANAGEMENT PLAN. 20
8.1.1. Project Governance Structure. 20
8.1.2. Project Management Team.. 20
8.2.4. Staff Transition on and off the Project Team.. 21
8.3. Project Human Resources Management 22
8.3.1.1. Human Resources Management Processes. 22
8.3.2. Human Resources Management Standards & Procedures. 22
8.3.3. Human Resources Management Methods, Tools & Techniques. 22
9. COMMUNICATION MANAGEMENT PLAN. 23
9.1. Communication Approach. 23
9.1.1. Communication Items. 23
9.1.2. Communication Matrix. 23
9.2. Project Communication Management 24
9.2.1. Communication Processes Management 24
9.2.2. Communication Management Standards & Procedures. 24
9.2.3. Communication Management Methods, Tools & Techniques. 24
10. STAKEHOLDER MANAGEMENT PLAN. 25
10.1. Stakeholder Management Approach. 25
10.1.1. Stakeholder Identification. 25
10.1.2. Power vs Interest Matrix. 25
10.1.3. Stakeholder Engagement Planning. 26
10.1.4. Stakeholder Engagement Management 26
10.1.5. Stakeholder Engagement Monitoring. 26
10.2. Project Stakeholder Management 26
10.2.1. Stakeholder Management Processes Management 26
10.2.2. Stakeholder Management Standards & Procedures. 26
10.2.3. Stakeholder Management Methods, Tools & Techniques. 26
11.2. Risk Management Process. 27
11.2.1. Risk Identification. 27
11.2.2. Qualitative Risk Assessment 27
11.2.3. Quantitative Risk Assessment 29
11.2.4. Risk Mitigation Planning. 29
11.2.7. Risk Contingency Budgeting. 29
11.3. Project Risk Management 29
11.3.1. Roles and Responsibilities. 29
11.3.2. Risk Management Standards & Procedures. 30
11.3.3. Risk Management Methods, Tools & Techniques. 30
12. CONFIGURATION MANAGEMENT PLAN. 31
12.1. Configuration Management Administration. 31
12.1.1. Configuration Management Environment 31
12.1.2. Configuration Identification. 31
12.1.5. Storage & Retention. 31
12.1.6. Configuration Control 32
12.1.7. Configuration Status Accounting. 32
12.1.8. Configuration Audits. 32
12.2. Project Configuration Management 32
12.2.1. Roles & Responsibilities 32
12.2.2. Configuration Management Standards & Procedures. 32
12.2.3. Configuration Management Methods, Tools & Techniques. 32
13. PROCUREMENT MANAGEMENT PLAN. 33
13.1. Project Procurement Approach. 33
13.1.1. Procurement Definition. 33
13.1.2. Procurement Process 33
13.1.5. Cost Determination. 33
13.1.6. Standardized Procurement Documentation. 34
13.1.7. Procurement Constraints. 34
13.1.8. Contract Approval Process. 34
13.1.11. Performance Metrics for Vendors. 34
13.2. Project Procurement Management 35
13.2.1. Roles & Responsibilities 35
13.2.2. Procurement Management Standards & Procedures. 35
13.2.3. Procurement Management Methods, Tools & Techniques. 35
14. Appendix: Referenced Documents. 36
Section 1. Project Management Plan Introduction
1.1. Version History and Sign-off
| Version | Reason for Change | Date of Approval | Approver’s Name |
| 1.0 | Initial Draft | dd/mm/yyyy | Joe Bloggs |
1.2. Purpose
The Project Management Plan (PMP) is a formal, approved document that defines how the project is going to be executed, monitored, and controlled. It is formed of subsidiary plans relating to each of the project knowledge areas (e.g. scope management, cost management), which can be referred to in the document or assembled into a single master document.
The PMP is developed in the Planning Phase by the Project Manager and provides detailed plans, processes, and procedures for managing and controlling the life cycle activities of a specific project, serving as the main reference for any element of the project team asking for guidance on the project. It should offer a comprehensive view of the project, its performance baselines, guidance and clear state ant tailoring applied to the relevant organizational standards (e.g. quality standards).
The PMP is a living document, subject to approval by the Project Sponsor/Board and formal configuration control.
1.3. Authorization
<List the names of the approvers of this Project Management Plan.>
| Approver’s Name | Job Title | Approved on (Date) | Signature |
2. SCOPE MANAGEMENT PLAN
The Scope Management Plan is the component of the Project Management Plan that describes how the scope will be defined, developed, monitored, controlled and verified
3.1. Project Scope Statement
3.1.1. Project Objectives
<List here your project objectives.>
| Project Objectives |
3.1.2. Project Scope Boundaries
<Provide a high-level description of the features and functions that characterize the product, service, or result that the project is meant to deliver. Explicitly state which areas of the organization (e.g. departments, regions) are going to be covered by the project. Complement this description by completing the table below, which sets the boundaries for the project scope, in this way reducing any potential ambiguity.>
| In Scope | Out of Scope |
3.2. Work Breakdown Structure
<List here the key deliverables and work packages that the project is required to produce to achieve the stated objectives. Include which criteria will be used for their acceptance and sign-off as well as estimated due date for completion. Add a graphical representation of the Work Breakdown Structure if available.>
| Deliverable Name | Acceptance Criteria | Due Date |
3.3. Expected Benefits
<Outline the key benefits to be realised by the project.>
| Project Benefits | Unit of Measure |
3.4. Key Project Assumptions
<Outline key project assumptions which can impact the project if proven false.>
| ID | Assumption | Importance | Impact if false |
3.5. Key Project Constraints
<Outline key project constraints which can impact the timescale, budget, or performance of the project.>
| ID | Constraint | Area of Impact |
3.6. Key Project Dependencies
<Outline key project dependencies to and from other projects.>
| ID | Dependency | Owner | Impact Date |
3.7. Project Success Criteria
<List the criteria on which the success of the project will be measured.>
| ID | Success Criteria |
3.8. Project Scope Management Approach
3.8.1. Scope Management Processes
<Describe how the project scope will be managed, including how changes to the scope will be addressed, and key roles and responsibilities.>
3.8.2. Scope Management Standards & Procedures
<Reference any organizational scope standards and procedures. Highlight any tailoring applied to these as part of this project.>
3.8.3. Scope Management Methods, Tools & Techniques
<List any preferred scope methods, tools and techniques that are going to be used in this project. Note any organizational tools and techniques which might be used by the project.
4. SCHEDULE MANAGEMENT PLAN
The Schedule Management Plan describes how the Project Schedule will be established and managed.
4.1. Project Schedule Approach
4.1.1. Task Definition
<Describe the approach for defining tasks, including creating and/or refining the Work Breakdown Structure (WBS), identifying durations, milestones, and dependencies, and determining the project critical path.>
4.1.2. Estimate Level of Effort
<Describe the approach for estimating level of effort. This section should include any automated tools used, historical data, factors, attributes, etc.>
4.1.3. Resource Allocation
<Describe the approach for allocating resources to tasks. If appropriate, refer to a separate Staffing Management Plan, if one exists.>
4.1.4. High-Level Timescale
<Use the diagram below to identify your key phases. Use the table below to identify the significant milestones or events in the project such as phases, stages, decision gates, or the approval of a deliverable. Refer to a separate project schedule (e.g. in an enterprise project management tool), if applicable.>
| Milestone | Description | Baseline Date |
4.1.5. Determining Schedule Changes
<Describe how changes to the Project Schedule will be identified.>
4.1.6. Obtaining Agreement on Schedule Changes
<Describe how agreement from the appropriate stakeholders will be obtained for proposed changes to the Project Schedule.>
4.1.7. Managing Schedule Changes
<Describe how changes to the Project Schedule will be managed. Include information regarding any tracking system that will be used, the frequency of reviews of the schedule, approval levels necessary for authorizing changes, variance analysis, and corrective actions.>
4.1.8. Measuring & Reporting Schedule Performance
<Describe how schedule performance will be measured and progress will be tracked. Include how often the Project Schedule will be reviewed/updated and how progress (% complete) will be determined.>.
4.2. Project Schedule Management
4.2.1. Schedule Management Processes
<Provide a summary of how the project schedule will be managed, including key roles and responsibilities.>
4.2.2. Schedule Management Standards & Procedures
<Reference any organizational schedule standards and procedures. Highlight any tailoring applied to these as part of this project.>
4.2.3. Schedule Management Methods, Tools & Techniques
<Describe the methods, tools and techniques tools that will be used to establish and store the master Project Schedule and any related subordinate schedules (e.g., Microsoft Project, Clarity, etc.). Also identify and describe any standard reports that will be used to measure and report the status of the Project Schedule (e.g., Gantt chart, network diagram).
5. COST MANAGEMENT PLAN
The Cost Management Plan is the outline of the project’s estimation, allocation and control of costs for the required resources to complete the project.
6. Project Cost Management Approach
6.1.1. Cost Baseline
<Identify what budget needs are anticipated, providing a rationale for each rubric. Additionally, outlines the various sources of funding that will be used to support the project. Refer to additional documentation where appropriate.>
| Estimate | Comment | |
| Revenue | ||
| Capital | ||
| Total Budget |
6.1.2. Cost Status Reporting
<Describe the requirements and procedures for cost status reporting. This should include specific requirements for format of financial status reports, distribution, security, frequency, reviews, etc.>
6.1.3. Invoicing
<Describe the requirements and procedures for invoicing. This should include specific requirements for format of invoices, distribution, security, frequency, quality assurance, etc.>
6.2. Project Cost Management
6.2.1. Roles & Responsibilities
<Identify key individuals responsible for cost management. Describe their responsibilities for activities such as invoicing, financial management tracking, etc. If appropriate, include an organizational chart illustrating the structure for the cost management organization.>
| Name | Role | Responsibility |
6.2.2. Cost Management Processes
<Provide a summary of how the project budget/cost will be managed, including changes to the baseline.>
6.2.3. Cost Management Standards & Procedures
<Reference any organizational cost standards and procedures. Highlight any tailoring applied to these as part of this project.>
6.3. Cost Management Methods, Tools & Techniques
<Describe the overall approach for cost management of the project, including how costs will be categorized, tracked, and reported. Describe the methods, processes, tools and techniques that will be used for cost management, and how they will integrate with other project processes (e.g., contract management, project monitoring and control, etc). Refer to additional documentation where appropriate.>
7. QUALITY MANAGEMENT PLAN
The Quality Management Plan determines quality policies and procedures relevant to the project for both project deliverables and project processes, defining who is responsible for what, and documenting the related processes for quality planning, assurance, and control.
7.1. Quality Management Approach
7.1.1. Quality Planning
<Identify which quality standards are relevant to the project and how to satisfy them. Identify and define appropriate quality metrics, including the acceptance criteria for project deliverables and product performance.>
7.1.2. Define Project Quality
<Identify quality standards and expectations for customers, the project, and the organization. Ensure that the customer and project success criteria are clear.>
| What is Quality? | What is Success? | |
| Customers | ||
| Project | ||
| Organization |
7.1.3. Measure Project Quality
<Describe how quality will be determined and measured. Identify desired metrics and related monitoring processes for which to measure quality standard. Additionally, define the methods of data collection and archiving, and document timeframe for measurement and metrics reporting.>
7.2. Quality Assurance & Quality Control
7.2.1. Assessments, Reviews & Audits
<Identify the product reviews, process audits, and other assessments that will be conducted during the project’s life cycle to ensure quality objectives and standards are met by completing the below.>
| Quality Review Type | Frequency | Triggering Event | Roles Involved |
7.2.2. Improve Project Quality
<Analyze quality data, document opportunities for improvement and apply what was learned from quality analysis to eliminate gaps between current and desired levels of performance.>
7.2.3. Quality Monitoring and Control
<Identify the monitoring and controlling actions that will be conducted to control quality throughout the project’s life.>
7.2.4. Corrective Actions
<Describe the process and procedures by which anomalies and problems will be recorded, tracked, resolved, and reported. Also, describe how corrective actions will be identified and communicated to the project team and stakeholders, how corrective action plans will be monitored, and who is responsible for assigning and executing these actions.>
7.3. Quality Schedule
<Provide a schedule of quality reviews and other quality activities planned for the project and/or refer to relevant additional documentation. Ensure that this information is appropriately integrated into the overall Project Schedule.>
7.4. Project Quality Management
7.4.1.1. Roles and Responsibilities
<Describe the primary roles and responsibilities of the project team as it relates to Quality Management for the project. Indicate responsibilities for activities such as mentoring or coaching, auditing work products, auditing processes, participating in project reviews, etc. If appropriate, include an organizational chart illustrating the structure for the quality management organization.>
| Name | Role | Responsibility |
7.4.1.2. Quality Management Processes
<Provide a summary of how the project quality will be managed, including changes to the baseline.>
7.4.2. Quality Management Standards & Procedures
<Reference any organizational cost standards and procedures. Highlight any tailoring applied to these as part of this project.>
7.4.3. Quality Management Methods, Tools & Techniques
<Describe the methods, processes, tools and techniques that will be used for quality management, and how they will integrate with other project processes (e.g., contract management, project monitoring and control, risk management, etc.).>
8. HUMAN RESOURCES MANAGEMENT PLAN
The Human Resources Management Plan documents when team members are added, managed, controlled, and released from the project. It also identifies and documents the project roles, responsibilities, and required skills.
8.1. Project Governance
8.1.1. Project Governance Structure
<Use the diagram below to illustrate the project governance structure, that is, which governance bodies and layers of governance will be involved in the project (e.g. project board, steering committees).
8.1.2. Project Management Team
<Identify who will be the members of the project management team as well as their role and main contact.>
| Name | Role | Contact |
| Project Sponsor | ||
| Project Manager | ||
| Project Assurance | ||
| <Role> | ||
| <Role> | ||
| <Role> |
8.2. Staffing Approach
8.2.1. Staff Required
<Present a detailed breakdown of the staff requirements by role needed to achieve the project objectives and execute the project. Describe how staffing needs will be managed throughout the project.>
| Role | Skills Required | Number of Staff Required | Assignment Start Date | Duration Required |
8.2.2. Staff Orientation
<Describe any information, forms, processes, or procedures that new staff must receive and/or complete prior to beginning work on the project (e.g., project travel policy, PPM tool access and guidance)>
8.2.3. Staff Development
<Identify staff training needs to ensure that necessary skill levels are available to successfully conduct the project.>
| Role | Training Required | Training Method | Anticipated Cost | Potential Vendors |
8.2.4. Staff Transition on and off the Project Team
<Describe the approach to allocating staff between each project lifecycle phase, and when and how staff will be transitioned on and off the project team.>
8.3. Project Human Resources Management
8.3.1.1. Human Resources Management Processes
<Provide a summary of how the project human resources will be managed, including key roles and responsibilities.>
8.3.2. Human Resources Management Standards & Procedures
<Reference any organizational cost standards and procedures. Highlight any tailoring applied to these as part of this project.>
8.3.3. Human Resources Management Methods, Tools & Techniques
<Describe the methods, processes, tools and techniques that will be used for staff management, and how they will integrate with other project processes (e.g., schedule management, contract management).>
9. COMMUNICATION MANAGEMENT PLAN
The Communications Management Plan defines the project’s structure and methods of information collection, screening, formatting, and distribution of project information. The overall objective of a Communications Management Plan is to promote the success of a project by meeting the information needs of project stakeholders.
9.1. Communication Approach
9.1.1. Communication Items
<Describe the approach for identifying communication items and list these communication items per stakeholder group:>
| Stakeholder Group | Communication Required | Frequency | Vehicle | Owner |
9.1.2. Communication Matrix
<Present the project Communication Matrix, which should clearly state which communication channels are allowed between the project team and other project stakeholders. Note the example provided below:>
9.1.3. Project Meetings
<Insert the project meeting schedule or provide a reference to where it is stored.>
| Meeting | Purpose | Frequency | Chair | Participants |
9.1.4. Project Reporting
<Insert the project reporting schedule or provide a reference to where it is stored.>
| Report | Purpose | Frequency | Owner | Distribution List |
9.2. Project Communication Management
9.2.1. Communication Processes Management
<Describe how project communications will be managed, including how changes to the Communication Matrix will be managed. Include processes for vetting communication messages and products, if necessary.>
9.2.2. Communication Management Standards & Procedures
<Reference any organizational communication standards and procedures. Highlight any tailoring applied to these as part of this project.>
9.2.3. Communication Management Methods, Tools & Techniques
<List any preferred methods, tools and techniques that are going to be used in this project. Note any organizational tools and techniques which might be used by the project (e.g. newsletters).
10. STAKEHOLDER MANAGEMENT PLAN
The Stakeholder Management Plan details the project’s activities related to engaging stakeholders and making the most effective use of their participation.>
10.1. Stakeholder Management Approach
10.1.1. Stakeholder Identification
<Describe the roles and interests, involvement, interest and power, and potential impact of each stakeholder groups on project success. Also, specify how the identification of new stakeholders will be accomplished throughout the project, including methods used (e.g. stakeholder interviews).>
| Stakeholder Group | Role on the Project | Level of Involvement | Level of Interest | Level of Impact | Engagement Strategy |
10.1.2. Power vs Interest Matrix
<Plot each of the stakeholder groups onto the Power vs Interest matrix. Note the example provided below.>
10.1.3. Stakeholder Engagement Planning
<Describe the planning of stakeholder engagement process, including roles and responsibilities. List each stakeholder group and place a “C” for their current level of engagement and “D” in the column of their desired level of engagement:>
| Stakeholder Group | Unaware | Resistant | Neutral | Supportive | Leading |
10.1.4. Stakeholder Engagement Management
<Describe the strategies and activities that will occur in the stakeholder engagement management process, including their ownership.>
10.1.5. Stakeholder Engagement Monitoring
<Describe how will the monitoring of stakeholder engagement be addressed by this project. Cleary describe how the Stakeholder Register and other tools, processes, and related procedures are going to be updated.>
10.2. Project Stakeholder Management
10.2.1. Stakeholder Management Processes Management
<Provide a summary of how project stakeholder management will be addressed.>
10.2.2. Stakeholder Management Standards & Procedures
<Reference any organizational stakeholder management standards and procedures. Highlight any tailoring applied to these as part of this project.>
10.2.3. Stakeholder Management Methods, Tools & Techniques
<List any preferred tools and techniques that are going to be used in this project. Note any organizational tools and techniques which might be used by the project (e.g. stakeholder questionnaires).>
11. RISK MANAGEMENT PLAN
The project Risk Management Plan described how risks are going to be identified, assessed, mitigated, monitored and closed in the project. It also clarifies roles and responsibilities and described the related risk tools and techniques to be used in the project.
11.1.1. Key Project Risks
<Outline the initial key project risks which can impact the project if they materialize. Provide a complete view of these risks in the project Risk Register.>
| ID | Risk | Probability | Impact | Mitigation Actions |
11.2. Risk Management Process
11.2.1. Risk Identification
<Describe the process for risk identification, including who is responsible for the identification of risks, what methods will be used to support the identification, as well as where, how, and when will new risks be recorded. Refer to the project Risk Register as needed.>
11.2.2. Qualitative Risk Assessment
<Describe the process for the qualitative analysis of risks, including the scale in use for probability, impact, and proximity, as well as the risk exposure ratings. Refer to the organizational risk procedures and scales as needed. Consider the examples below.>
Risk Exposure Rating:
| Risk Exposure Rating | Description | Color Code |
| HIGH (H) | Unacceptable. Major disruption likely; different approach required; priority management attention required. | Red |
| MODERATE (M) | Some disruption; different approach may be required; additional management attention may be needed. | Yellow |
| LOW (L) | Minimum impact; minimum oversight needed to ensure risk remains low. | Green |
Probability:
| Rating | Value Assigned | Probability of Occurrence |
| Near Certainty | 0.90 | ~90% |
| Highly Likely | 0.70 | ~70% |
| Likely | 0.50 | ~50% |
| Low Likelihood | 0.30 | ~30% |
| Not Likely | 0.10 | ~10% |
Impact:
| Rating | Value Assigned | Program Impact | Technical Impact | Cost Impact | Schedule Impact |
| Marginal | 0.05 | Remedy will cause program disruption | Performance goals met, no impact on program success | Program budget not dependent on issue; no impact on program success; development or production cost goals not exceeded or dependent on this issue | Schedule not dependent on this issue; no impact on program success; development schedule goals not exceeded or not dependent on the issue |
| Significant | 0.10 | Shorts a significant mission need | Performance below goal, but within acceptable limits. No changes required, acceptable alternatives exist, minor impact on program success | Program budget impacted by < 1%; minor impact on program success; development or production cost goals exceeded by 1 – 5%; program management resources do not need to be used to implement workarounds | Non-critical path activities late; workarounds would avoid impact on key and non-key program milestones; minor impact on program success, development schedule goals exceeded by 1-5% |
| Serious | 0.20 | Shorts a critical mission need | Performance below goal, moderate changes required, alternative would provide acceptable system performance, limited impact on program success | Program budget impacted by 1 – 5%; limited impact on program success; development or production cost goals exceeded by 5 – 15%; program management reserves do not need to be used to implement workarounds | Critical path activities one month late; workarounds would not meet program milestones; program success in doubt; development schedule goals exceeded by 5-10% |
| Very Serious | 0.40 | Potentially fails key performance parameter | Performance unacceptable; significant changes required; possible alternatives may exist; program success in doubt | Program budget impacted by 5-10%; program success in doubt; development or production cost goals exceeded by 15-20%; program management reserves must be used to implement workarounds | Critical path activities one month late; workarounds would not meet program milestones; program success in doubt; development schedule goals exceed by 10 -15% |
| Catastrophic | 0.80 | Jeopardizes an exit criterion of current acquisition phase | Performance unacceptable; no viable alternatives exist; program success jeopardized | Program budget impacted by 10%; program success jeopardized; development or production cost goals exceeded by 20 – 25% | Key program milestones would be late by more than 2 months; program success jeopardized; development schedule goals exceeded by 20% |
Proximity:
| Proximity Levels | Description |
| Within the Stage | The risk is expected to cause an impact in the current project stage |
| Within the Project | The risk is expected to cause an impact in the project but is outside the current stage |
| Outside the Project | The risk is expected to cause an impact in the objectives/benefits of the project, post-project implementation |
11.2.3. Quantitative Risk Assessment
<Describe the process regarding the quantitative analysis of risks, that is, how the financial impact of the risk will be assigned, assessed, monitored, and mitigated. Refer to any organizational risk management procedures as applicable.>
11.2.4. Risk Mitigation Planning
<Describe the process for risk mitigation planning, including the risk mitigation responses and how these are expected to be implemented. Refer to any organizational risk management procedures as applicable.>
11.2.5. Risk Tracking
<Describe the methods and metrics that will be used to track the project’s risk status throughout the lifecycle as well as how this status will be reported to the stakeholders/ management.>
11.2.6. Risk Closing
<List the criteria when a risk can be closed and state who has the authority to close a risk.>
11.2.7. Risk Contingency Budgeting
<Should a risk contingency budget have been allocated for risk management activities, state here, clearly defining how access to that budget will be triggered, tracked, and reported on.>
11.3. Project Risk Management
11.3.1. Roles and Responsibilities
<Describe the primary roles and responsibilities of the project team as it relates to Risk Management for the project. Indicate responsibilities for activities such as identifying risks, updating risk registers, implementing mitigation actions, etc. If appropriate, include an organizational chart illustrating the structure for the risk management organization.>
| Name | Role | Responsibility |
11.3.2. Risk Management Standards & Procedures
<Reference any organizational risk management standards and procedures. Highlight any tailoring applied to these as part of this project.>
11.3.3. Risk Management Methods, Tools & Techniques
<Describe which methods, tools and techniques will be used to support the risk management processes. Should there be organizational standards in this regard, please state them here, including any tailoring made as part of this project.>
12. CONFIGURATION MANAGEMENT PLAN
The project Configuration Management Plan covers the project approach for the identification, baselining, tracking, storage and distribution of configuration items in the project. It also describes the related configuration management processes and key roles and responsibilities.
12.1. Configuration Management Administration
12.1.1. Configuration Management Environment
<Describe the technical architecture, setup, and maintenance of the Configuration Management environment. Refer to technical documentation where appropriate.>
12.1.2. Configuration Identification
<Describe the process for identifying and documenting the items that are to be placed under configuration control.>
12.1.3. Naming Standard
<Describe the standard convention to be followed for uniquely naming configuration items.>
12.1.4. Baselines
<Identify and describe the types of configuration baselines that will be established for the project (e.g. functional, product, management) which reside outside this document.>
12.1.5. Storage & Retention
<Describe how the configuration items are to be retained and recorded in the project inventory (e.g., online, offline, media type, and format). Refer to any organizational standards and procedures as applicable.>
| Configuration Item | Storage | Retention |
12.1.6. Configuration Control
<Identify when configuration items will be placed under configuration control. Identify and briefly describe the control mechanisms that will be used for establishing baselines and ensure appropriate change control to those configuration items.>
12.1.7. Configuration Status Accounting
<Describe the process for recording and reporting information needed to maintain the integrity and traceability of controlled configuration items and associated documentation throughout the project.>
12.1.8. Configuration Audits
<Describe the process for performing internal and external configuration audits of identified and controlled configuration items.>
12.2. Project Configuration Management
12.2.1. Roles & Responsibilities
<Identify key individuals responsible for configuration management. Describe their responsibilities for activities such as configuration identification, configuration control, configuration auditing/reporting, etc for software, hardware, and documentation. If appropriate, include an organizational chart to illustrate the different roles and responsibilities.>
| Name | Role | Responsibility |
12.2.2. Configuration Management Standards & Procedures
<Reference any organizational configuration management standards and procedures. Highlight any tailoring applied to these as part of this project.>
12.2.3. Configuration Management Methods, Tools & Techniques
<Describe the methods, processes, tools and techniques that will be used for configuration management, and how they will integrate with other project processes (e.g. change management, quality management, contract management, etc.).>
13. PROCUREMENT MANAGEMENT PLAN
The project Procurement Management Plan defines the procurement requirements for the project and how it will be managed from developing procurement documentation through contract closure.
13.1. Project Procurement Approach
13.1.1. Procurement Definition
<Describe, in specific terms, what items will be procured, their justifications and related timescale conditions that must be met. Any important technical information should also be included.>
| Item | Justification | Needed By |
13.1.2. Procurement Process
Outline the procurement process to be used, including the need for a Request for Quote (RFQ), Request for Proposal (RFP) or a Request for Bid (RFB).>
13.1.3. Contract Type
<Describe the type of contract to be used (e.g. fixed-price, time and materials), including clauses specific to the project, so the contracts and procurement department can proceed accordingly.>
13.1.4. Procurement Risks
<Describe how risks related specifically to procurement activities will be managed. Refer to the Risk Management Plan where applicable.>
13.1.5. Cost Determination
<Describe how costs will be determined and if/how they will be used as part of the selection criteria of vendors.>
13.1.6. Standardized Procurement Documentation
<Describe what standard procurement documentation will be used as part of the procurement. Refer to organizational standards where needed.>
13.1.7. Procurement Constraints
<Describe any constraints which must be considered as part of the project’s procurement management process. These constraints may be related to schedule, cost, and scope, resources, technology, or buyer/seller relationships.>
13.1.8. Contract Approval Process
<Define the process through which contracts must be approved.>
13.1.9. Decision Criteria
<Define the criteria used by the contract review board to decide on what contract(s) to award>
| Decision Criteria | Acceptable Range | Weight |
13.1.10. Vendor Management
<Describe the roles and actions the project team and purchasing and contracts department will take to ensure that the selected vendors provide all of the products/services agreed upon and that the appropriate levels of quality are maintained.>
13.1.11. Performance Metrics for Vendors
<Describe the metrics to be used for procurement activities associated with the project. Note the example below.>
| Vendor | Product Quality | On Time Delivery | On Budget Delivery | Documentation Quality | Transactional Efficiency | Support post-delivery |
1 – Unsatisfactory
2 – Acceptable
3 – Exceptional
13.2. Project Procurement Management
13.2.1. Roles & Responsibilities
<Identify key individuals responsible for procurement management. If appropriate, include an organizational chart to illustrate the different roles and responsibilities.>
| Name | Role | Responsibility |
13.2.2. Procurement Management Standards & Procedures
<Reference any organizational procurement management standards and procedures. Highlight any tailoring applied to these as part of this project.>
13.2.3. Procurement Management Methods, Tools & Techniques
<Describe the methods, processes, tools and techniques that will be used for procurement management, and how they will integrate with other project processes (e.g. change management, quality management, scope management, etc.).>
14. Appendix: Referenced Documents
Summarize the relationship of this document to other relevant documents. Provide identifying information for all documents used to arrive at and/or referenced within this document (e.g., related and/or companion documents, prerequisite documents, relevant technical documentation, etc.).
| Document Name | Document Location / URL | Latest Version |