week 9

<Project Name>

project Management plan

Version <1.0>

<mm/dd/yyyy>

VERSION HISTORY

[Provide information on how the development and distribution of the Project Management Plan was controlled and tracked. Use the table below to provide the version number, the author implementing the version, the date of the version, the name of the person approving the version, the date that particular version was approved, and a brief description of the reason for creating the revised version.]

Version #	Implemented By	Revision Date	Approved By	Approval Date	Reason
1.0	<Author name>	<mm/dd/yy>	<name>	<mm/dd/yy>	<reason>

Template Version: 03/18

Note to the Author

[This document is a template of a Project Management Plan document for a project. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project.

· Blue italicized text enclosed in square brackets ([text]) provides instructions to the document author, or describes the intent, assumptions and context for content included in this document.

· Blue italicized text enclosed in angle brackets (<text>) indicates a field that should be replaced with information specific to a particular project.

· Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to a specific project. These are offered only as suggestions to assist in developing project documents; they are not mandatory formats.

When using this template for your project document, it is recommended that you follow these steps:

1. Replace all text enclosed in angle brackets (e.g.,, <Project Name>) with the correct field values. These angle brackets appear in both the body of the document and in headers and footers. To customize fields in Microsoft Word (which display a gray background when selected):

a. Select File>Properties>Summary and fill in the Title field with the Document Name and the Subject field with the Project Name.

b. Select File>Properties>Custom and fill in the Last Modified, Status, and Version fields with the appropriate information for this document.

c. After you click OK to close the dialog box, update the fields throughout the document with these values by selecting Edit>Select All (or Ctrl-A) and pressing F9. Or you can update an individual field by clicking on it and pressing F9. This must be done separately for Headers and Footers.

2. Modify boilerplate text as appropriate to the specific project.

3. To add any new sections to the document, ensure that the appropriate header and body text styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and Heading 3. Style used for boilerplate text is Body Text.

4. To update the Table of Contents, right-click and select “Update field” and choose the option- “Update entire table”

5. Before submission of the first draft of this document, delete the “Notes to the Author” page and all instructions to the author, which appear throughout the document as blue italicized text enclosed in square brackets.]

6. Do not delete sections or state "not applicable"

7. Requirements state the “what” and are not to state the “why” or “how”

8. Requirements should include “shall”, not “will” or other words - be definitive

a. Review the requirement information in the course and text content

9. The timeline, requirements, and milestones shall all align and build the objectives

a. The objectives are defined by the requirements

b. The milestones should be scheduled in the timeline

10. The objectives, deliverables, timelines, assumptions, risks, requirements, assumptions, etc should always align and sync with the scope of the project

a. Validate they all say the same things

b. Ensure they all reference the same aspects of the project and focus toward the same clear, concise goals

11. Every artifact is a formal document

a. Do not use the words “I”, “we”, “our”, “you”, “they”, "my mom", "my wife", etc

b. Use “The Project Team”, “The business owner”, etc

12. You are the Project Manager

a. This project may be working on your house, but the homeowner is the business owner and you are leading this project (as the Project Manager)

13. Stakeholders are anyone who impact or can be impacted by the project and/or its success (or failure)

14. Do not be vague

a. Be specific and precise in your verbiage

b. Focus your language

c. Focus and narrow your scope

i. The reader should not be confused as to what specifically your project will deliver, with outcomes

ii. The artifacts shall be specific and stating exactly what your project will entail, the objectives, and how they will be created

15. Define all acronyms on their first use

16. Update all deliverables, once graded, with the feedback provided

17. Attach (imbed) all attachments in the Appendix B References section of the final Project Management Plan

a. Do not state the “attachments are located on the SharePoint site” or "located on paper in my office"

b. These documents should be standalone documents and self-contained

c. To imbed the artifacts - Click in the spot you want the document to appear; Insert - Object; Create From File - Browse - Select your file - Insert - Display as Icon - OK

18. Deliverables are outputs of the project, or phase, or process

a. They are what you are working towards in your ultimate project output

19. Mitigation strategies are how you will manage the risks

20. The blue font indicates instructions and notes on the templates

a. Read the instructions (blue font)

b. The blue font should be removed or updated to match document font, prior to submission

21. The font and formatting has to be consistent through the document; this includes capitalization, grammar, etc

22. Always spell check everything

TABLE OF CONTENTS

4 1 Introduction

4 1.1 Purpose of Project Management Plan

4 2 Executive Summary of Project Charter

4 2.1 Assumptions/Constraints

4 3 Scope Management

4 3.1 Work Breakdown Structure

4 3.2 Deployment/Implementation Plan

4 3.3 Change Control Management

4 4 Schedule/Time Management

5 4.1 Milestones

5 4.2 Project Schedule

5 4.2.1 Dependencies

5 5 Cost/Budget Management

5 6 Quality Management

5 7 Human Resource Management

5 8 Communications Management

5 8.1 Communication Matrix

5 9 Risk Management

6 9.1 Risk Register

6 10 Issue Management

6 10.1 Issue Log

6 11 Procurement Management

6 12 Compliance Related Planning

7 Appendix A: Project Management Plan Approval

8 APPENDIX B: REFERENCES

9 APPENDIX C: KEY TERMS

10 APPENDIX D: SUMMARY OF SPENDING

1 Introduction

1.1 Purpose of Project Management Plan

[Provide the purpose of the project and project management plan – describe the business need it fulfills.]

The intended audience of the <Project Name> Project Management Plan (PMP) is all project stakeholders including the project sponsor, senior leadership and the project team.

2 Executive Summary of Project Charter

[Provide an executive summary of the project – from the Project Charter - attach it to Appendix B.]

2.1 Assumptions/Constraints

[Insert a summary of the current project assumptions and/or constraints.]

3 Scope Management

[Describe how the scope of the project will be managed throughout the lifecycle of the project.]

3.1 Work Breakdown Structure

[Create and insert the project’s work breakdown structure.]

3.2 Deployment/Implementation Plan

[Describe how the project will be deployed, implemented, etc.]

[Example: The project involves deploying an application to state health partners. This section would discuss the approach for rolling out the application to the end users, including conducting environment assessments, developing memorandums of understandings, hardware/software installation, data conversion.]

3.3 Change Control Management

[Describe how changes to the project, requirements, deliverables, milestones, etc will be managed throughout the project lifecycle.]

[Example of Change Control: If a development server for your project is administered by another organization that is responsible for installing machine upgrades and there are scheduled outages that will impact your project schedule. Changes to the project will need to be made to deal with the potential impact of the scheduled outage.]

4 Schedule/Time Management

[Describe how changes to the project’s schedule or time requirements will be managed throughout the project lifecycle.]

[Example of schedule management approach: Establish a baseline within the first two weeks of the project and monitor progress against the baseline on a weekly basis. The Project Manager will be responsible for ensuring the project schedule is updated with the latest information and never more than three business days out of date. the Executive Steering Committee must approve variances on greater than 10% .]

4.1 Milestones

The table below lists the milestones for this project, along with their estimated completion timeframe.

Milestones	Estimated Completion Timeframe
[Insert milestone information (e.g., Project planned and authorized to proceed)]	[Insert completion timeframe (e.g., Two weeks after project concept is approved)]
[Add additional rows as necessary]

4.2 Project Schedule

[Insert the project’s schedule – be sure to include the month and year. Itemize each activity and expected start and completion time – insert the GANTT Chart.]

4.2.1 Dependencies

[Insert the schedule/project dependencies (both internal and external). N example of dependencies – If “this” does not get completed on time, then “this” cannot occur as planned/needed such as – Office of Information Technology (OIT) Recommendations - If OIT does not complete their evaluation of system A and provide its recommendations by September 30, 2018, the interface between system A and system B cannot be completed timely. ]

5 Cost/Budget Management

[Describe how the budget and project costs will be managed throughout the project lifecycle – include the utilization of reserves.]

6 Quality Management

[Describe how project quality will be evaluated and managed throughout the project lifecycle.]

[Example: For an information system, controlling the consistency of screen layouts would include reviewing all screens to make sure they match the standards. Quality measures may be no bugs or defects for certain critical requirements, consistent screen layouts, or correctly calculating variables. Quality may be ensured through inspections, audits, formal testing and documentation of defects in a defect tracking system to ensure defects are fixed, retested and closed. Some projects may choose to use a traceability matrix to determine if critical requirements have been met.]

7 Human Resource Management

[Describe how the staffing, personnel, resources, etc will be managed. Explain if there be hired staff, contractors, internal support to finish the product, etc. .]

8 Communications Management

[Describe how project communications – format, frequency, with whom, etc - will be managed throughout the project lifecycle. If the Communications Management Plan was completed as a previous submission, update and attach it to Appendix B.]

8.1 Communication Matrix

[Create and insert the project’s communication matrix – modify the table or enter the updated matrix from the previous submission..]

Stakeholder	Messages	Vehicles	Frequency	Communicators	Feedback Mechanisms

9 Risk Management

[Describe how risks – and the decisions used when elevating risks to issues - will be identified, evaluated, prioritized, managed, etc throughout the project lifecycle.]

9.1 Risk Register

[Create a risk register, include any current issues.]

10 Issue Management

[Describe how project issues – risks which have been elevated and are impacting the project - will be identified, evaluated, managed, etc throughout the project lifecycle.]

10.1 Issue Log

[Create an issue log and insert it here.]

11 Procurement Management

[Describe how purchases, contract, supplies, etc will be obtained and managed throughout the project lifecycle.]

[Example: This can include information such as ensuring project team members are assigned computers, how development and test servers are procured or can go into more detail and include an acquisition strategy that details how the project will be staffed (e.g., performance based fixed price contract, contractors).]

12 Compliance Related Planning

[Insert a list of compliance related processes the project must adhere to throughout the project lifecycle.]

Appendix A: Project Management Plan Approval

The undersigned acknowledge they have reviewed the <Project Name> Project Management Plan and agree with the approach it presents. Changes to this Project Management Plan will be coordinated with and approved by the undersigned or their designated representatives.

[List the individuals whose signatures are desired. Examples of such individuals are Business Owner, Project Manager or Project Sponsor. Add additional lines for signature as necessary. Although signatures are desired, they are not always required to move forward with the practices outlined within this document.]

Signature:		Date:
Print Name:
Title:
Role:

Signature:		Date:
Print Name:
Title:
Role:

Signature:		Date:
Print Name:
Title:
Role:

APPENDIX B: REFERENCES

[Insert all updated artifacts submitted in this course to this table, include name, version number, description, and location of any documents referenced in this document. Add rows to the table as necessary. Documents which should be attached here: Project Charter, Stakeholder Management Plan, Communications Management Plan, Risk Management Plan, Risk Register (if not included in the content section), and any other artifacts created, as applicable. ]

To imbed the artifacts - Click in the spot you want it to appear (Location column); Insert - Object; Create From File - Browse - Select your file - Insert - Display as Icon - OK ]

The following table summarizes the documents referenced in this document.

Document Name and Version	Description	Location
<Document Name and Version Number>	[Provide description of the document]	<Attach the document here>

APPENDIX C: KEY TERMS

[Insert terms and definitions used in this document. Add rows to the table as necessary. Follow the link below to for definitions of project management terms and acronyms used in this and other documents. ]

The following table provides definitions for terms relevant to this document.

Term	Definition
[Insert Term]	[Provide definition of the term used in this document.]
[Insert Term]	[Provide definition of the term used in this document.]
[Insert Term]	[Provide definition of the term used in this document.]

APPENDIX D: SUMMARY OF SPENDING

[To modify/edit the table - double-click on the table. Be sure to tailor the headings and contents to meet the needs of your project and include Contingency Reserves and Management Reserves.]