Project Plan
<Project Name> (HRS-xxxxx)
Contents
1.General Overview
1.1Document Change Control
1.2Definitions
2.Project Plan Approval Signatures
2.1Project Manager
2.2Project Sponsor
2.3Project Customer
2.4Project Customer
3.Project Plan Overview, Scope, Critical Assumptions, Requirements, and Success Criteria
3.1Overview
3.2Scope
3.3Assumptions
3.4Requirements
3.5Success Criteria
4.Project Work Plans
4.1Work Breakdown Structure
4.2Roles and Responsibilities
4.3Project Schedule
4.4Project Budget (if applicable)
5.Project Control Plans
5.1Change Management Plan
5.2Quality Management Plan
5.3Issue Management Plan
5.4Scope Management Plan
5.5Risk Management Plan
5.6Procurement Plan (if applicable)
5.7Support Transition Plan
6.Appendix
6.1Work Breakdown Structure
6.2Change Management Plan
6.3Quality Management Plan
6.4Issue Management Plan
6.5Scope Management Plan
6.6Risk Management Plan
6.7Procurement Plan
6.8Support Transition Plan
1.General Overview
1.1Document Change Control
The following is the document control for revisions to this document.
Version Number / Date of Issue / Author(s) / Brief Description of Change1.2Definitions
The following are definitions of terms, abbreviations and acronyms used in this document.
Term / Definition2.Project Plan Approval Signatures
2.1Project Manager
SignatureDate
[Name]
[Position]
[Organization]
2.2Project Sponsor
SignatureDate
[Name]
[Position]
[Organization]
2.3Project Customer
SignatureDate
[Name]
[Position]
[Organization]
2.4Project Customer
SignatureDate
[Name]
[Position]
[Organization]
3.Project Plan Overview, Scope, Critical Assumptions, Requirements, and Success Criteria
3.1Overview
The purpose of the Project Plan is to present the detail required to successfully execute and control the project, facilitate communication among project stakeholders, and document approved schedule baselines. The project plan is a living document and will evolve over time as more information about the project becomes available.
The project plan is developed based on scope items as noted in the Project Charter. Any changes to the scope items may impact the project schedule and/or the project quality. Any changes to the approved project scope must go through the scope change management process.
[Insert project plan overview here]
3.2Scope
The project plan is developed based on scope items as noted in the Project Charter. Any changes to the scope items may impact the project schedule and/or the project quality. Any changes to the approved project scope must go through the scope change management process. The scope items are:
[Insert scope items from Project Charter here]
3.3Assumptions
The project plan is developed based upon certain key assumptions as noted in the Project Charter. Any changes to these assumptions may impact the project schedule, projected costs, the project scope and/or the project quality. These assumptions are:
[Insert assumptions here]
3.4Requirements
The project scope is further defined by requirements. The requirements are:
[Insert requirements here]
3.5Success Criteria
The project success relies on defined success criteria. The success criteria are both objective and subjective:
- Was the outcome successful considering the initial needs and how well it was met? This is the measurement of deliverables success.
- Was the project managed in a successful way considering how well it was organized, structured and executed, including timeliness, cost control, effectiveness of the project plan, and adherence to established project management standards? This is the measurement of process success.
- Did the "human element" perform successfully considering stakeholder engagement, teamwork, collaboration, communication and cooperation? This is the measurement of performance success.
[Provide the project success criteria here.]
4.Project Work Plans
4.1Work Breakdown Structure
The work breakdown structure identifies the project’s tasks to provide a framework for organizing and managing the work of the project.
[Insert work breakdown structure here or attach as appendix.]
4.2Roles and Responsibilities
The purpose of the staffing plan is to make certain the project has sufficient staff with the right skills and experience to ensure a successful project completion. A complete listing of project roles’ responsibilities may be found in the “Project Team – Roles and Responsibilities” document.
[Insert staffing plan here. Example fields include: Role, Name, Start Date, End Date, Required FTEs]
4.3Project Schedule
The project schedule includes milestones, task dependencies, task duration, delivery dates, and staff resources assigned to complete the tasks.
[Insert project schedule here.]
4.4Project Budget (if applicable)
The project budget describes cost and budget needed to complete the project tasks.
[Insert project budget here. Example fields include: Cost Type, FY-yy-yy, FY-zz-zz, Total]
5.Project Control Plans
Project Control Plans provide the basis to control and monitor the progress of the project.
The Project Control Plan includes the following detail plans that can be found in the Appendix:
[Delete the description of the detail plans that are not included.]
5.1Change Management Plan
Defines the information needs of the project stakeholders and the project team by documenting what, when, where, and how information will be distributed.
The (project name) will utilize the UW Service Center change management methodology (depicted below) and detailed in the Change Management Methodology document (link).
[Using the information from the Project Charter document, provide the detailed change management approach/strategy for the project, as determined by the project’s change sponsor and project team. Provide a link to the Change Management Plan document in the appendix below.]
[Provide a statement related to project readiness criteria. Provide detailed project readiness information in the project plan appendix.]
5.2Quality Management Plan
Provides a plan that defines the quality control and quality assurance activities to be performed during the course of the project and the resources responsible for project quality control and assurance activities.
5.3Issue Management Plan
Defines how issues are identified, evaluated, assigned and tracked for resolution.
5.4Scope Management Plan
Provides a scope management process for changes to project scope, schedule, budget and quality. Defines how changes are identified, evaluated, assigned and tracked for resolution.
5.5Risk Management Plan
Provides a plan to manage risk management throughout the project. Defines how risks are identified, evaluated, monitored and remedied.
5.6Procurement Plan (if applicable)
Identifies those needs for the project which can be met by purchasing products or services from outside of the organization. Includes information about major procurements, procurement strategies, and projected dates for critical procurement activities.
5.7Support Transition Plan
Summarizes tasks to prepare for transition to support organization. Includes projected dates for completing documentation and review of Change Management request, Configuration Management, Help Desk, and Service Management.
6.Appendix
[Insert each detail plan after the corresponding heading in the following list. Another option is to include a link under the corresponding heading to the detailed plan stored in your project repository. Delete the headings of the plans that are not included. To prepare a plan, refer to applicable templates for each plan.]
6.1Work Breakdown Structure
6.2Change Management Plan
6.3Quality Management Plan
6.4Issue Management Plan
6.5Scope Management Plan
6.6Risk Management Plan
6.7Procurement Plan
6.8Support Transition Plan
Page 1 of 87/15/2014