Project Name$>$

Project Management Plan

Prepared by:

Date:

TABLE OF CONTENTS

INTRODUCTION $2$

PROJECT MANAGEMENT APPROACH $2$

PROJECT SCOPE $2$

MILESTONE LIST $2$

SCHEDULE BASELINE AND WORK BREAKDOWN STRUCTURE $2$

CHANGE MANAGEMENT PLAN $3$

COMMUNICATIONS MANAGEMENT PLAN $3$

COST MANAGEMENT PLAN $4$

PROCUREMENT MANAGEMENT PLAN $4$

PROJECT SCOPE MANAGEMENT PLAN $4$

SCHEDULE MANAGEMENT PLAN $4$

QUALITY MANAGEMENT PLAN $5$

RISK MANAGEMENT PLAN $5$

RISK REGISTER $5$

STAFFING MANAGEMENT PLAN $5$

RESOURCE CALENDAR $5$

COST BASELINE $6$

QUALITY BASELINE $6$

SPONSOR ACCEPTANCE $7$

INTRODUCTION

The Introduction provides a high level overview of the project and what is included in this Project Management Plan. This should include a high level description of the project and describe the projects deliverables and benefits. Excessive detail is not necessary in this section as the other sections of the project plan will include this information. This section should provide a summarized framework of the project and its purpose. Look back at the Project Charter for information to include in this section.

PROJECT MANAGEMENT APPROACH

This section is where you outline the overall management approach for the project. This section should describe, in general terms, the roles and authority of project team members. It should also include which organizations will provide resources for the project and any resource constraints or limitations$.$ If there are any decisions which must be made by specific individuals$$for example authorizing additional funding by the project sponsor$$this should also be stated here. It should be written as an Executive Summary for the Project Management Plan.

PROJECT SCOPE

State the scope of the project in this section. The scope statement from the project charter should be used as a starting point; however, the project plan needs to include a much more detailed scope than the charter. This detail should include what the project does and does not include. The more detail included in this section, the better the product. This will help to clarify what is included in the project and help to avoid any confusion from project team members and stakeholders.

MILESTONE LIST

Provide a summary list of milestones including dates for each milestone. Include an introductory paragraph in this section which provides some insight to the major milestones. This section should also mention or discuss actions taken if any changes to the milestones or delivery dates are required.

Milestone Description Date

SCHEDULE BASELINE AND WORK BREAKDOWN STRUCTURE

This section should discuss the WBS$,$ WBS Dictionary, and Schedule baseline and how they will be used in managing the project$$s scope. The WBS provides the work packages to be performed for the completion of the project. The WBS Dictionary defines the work packages. The schedule baseline provides a reference point for managing project progress as it pertains to schedule and timeline. The schedule baseline and work breakdown structure $($WBS$)$ can be created in Microsoft Project if available. The WBS can be exported from the MS Project file.

CHANGE MANAGEMENT PLAN

This section should describe your change control process. Ideally, this process will be some type of organizational standard which is repeatable and done on most or all projects when a change is necessary. Changes to any project must be carefully considered and the impact of the change must be clear in order to make any type of approval decisions. Many organizations have change control boards $($CCBs$)$ which review proposed changes and either approve or deny them. This is an effective way to provide oversight and ensure adequate feedback and review of the change is obtained. This section should also identify who has approval authority for changes to the project, who submits the changes, how they are tracked and monitored.

For complex or large projects the Change Management Plan may be included as an appendix to the Project Management Plan or as a separate, stand$-$alone document.

COMMUNICATIONS MANAGEMENT PLAN

The purpose of the Communications Management Plan is to define the communication requirements for the project and how information will be distributed to ensure project success. You should give considerable thought to how you want to manage communications on every project. By having a solid communications management approach you$$ll find that many project management problems can be avoided. In this section you should provide an overview of your communications management approach. Generally, the Communications Management Plan defines the following:

$$ Communication requirements based on roles

$$ What information will be communicated

$$ How the information will be communicated

$$ When will information be distributed

$$ Who does the communication

$$ Who receives the communication

$$ Communications conduct

For larger an