Project Management Plan

[Overview of Executive Summary Comment by Loran: Delete this Overview and comment BEFORE submitting assignment u05a1.

E

xecutive Summaries are exactly what they imply, a brief description of the project that a busy executive may read to understand the purpose, main points, and deliverables of a project. They are tailored so upper management understands how the project fits into the mission and goals of the organization.

Unlike the aforementioned templates in this document the Executive Summary is known for its brevity. However, the importance of this template is to be able to recognize and report the most important things the executives need to know so there are no “surprises” during the project run.

NOTE: THIS WILL BE THE LAST THING YOU WILL FINISH IN THIS DOCUMENT BUT IT USUALLY APPEARS AT THE BEGINNING OF THE PROJECT PLAN.]

Table of Contents Comment by Loran: This document uses the MS Word Table of Contents (TOC) feature. Use the MS Word help menu to find out more if you’ve never used this feature. DELETE this comment before submitting this document for the first time.

Executive Summary 1 Version Control 5 Project Charter 6 Preliminary Scope Statement 9 Project Scope 13 Work Breakdown Structure (WBS) 14 Budget 17 Communications Matrix 18 Risk Matrix 19 Project Schedule 21 Project Quality Plan 22 Introduction 22 Plan Quality Management Processes: 22 Inputs: 22 Tools & Techniques: 22 Outputs: 22 Perform Quality Assurance: 22 Inputs: 22 Tools & Techniques: 22 Outputs: 22 Control Quality: 22 Inputs: 22 Tools & Techniques: 22 Outputs: 22 Project Human Resource Plan 23 Introduction 23 Plan Human Resource Management 23 Inputs: 23 Tools & Techniques: 23 Outputs: 23 Acquire Project Team 23 Inputs: 23 Tools & Techniques: 23 Outputs: 23 Develop Project Team 23 Inputs: 23 Tools & Techniques: 23 Outputs: 24 Manage Project Team 24 Inputs: 24 Tools & Techniques: 24 Outputs: 24 Project Procurement Plan 24 Introduction 24 Plan Procurement Management 24 Inputs: 24 Tools & Techniques 24 Outputs: 24 Conduct Procurement Management 24 Inputs: 24 Tools & Techniques 24 Outputs: 24 Control Procurement Management 25 Inputs: 25 Tools & Techniques 25 Outputs: 25 Close Procurement Management 25 Inputs: 25 Tools & Techniques 25 Outputs: 25 References 26 Appendices 27

[OVERVIEW OF VERSION CONTROL: Any change should be documented. For example if I (the instructor) send this document back to you for revisions, the revision should be number and dated. So if I send it back to a learner after the learner submits this template the first time, it should have a second row of 1.1, u01a1, date of submission.]

[OVERVIEW OF PROJECT CHARTER: Comment by Loran: Delete this overview section and comment BEFORE submitting assignment u01a1.

C

harters establish the project within the organization and recognize the project manager as the person in charge of resources (Human Resources, Money, Procurement, etc.) and the ability to utilize those resources. It defines what is known at the beginning of the project such as the Title, Timeframe, Starting Budget, Project Manager, Approach, and roles and responsibilities of the team members. Many projects experience “progressive elaboration” or in other words, more is known about the project as it moves along.]

Project Title: [Enter the Project Plan Title here.]

Project Start Date: Click here to enter a date. Project Finish Date: Click here to enter a date.

Budget: [This is an overall amount that was set at the beginning of the project. However any known specifics should be put in as well.]

Project Manager: [Your name]

Project Objectives: [Put in what are the deliverables to the project. This may include the end product or service. There may be training of employees involved or other follow-ups at the end of the project. The documents and documentation of the project are deliverables as well.]

Approach: [A description on HOW the Project Objectives (From Above.) will be accomplished.]

[Individual items and how they are to be implemented.]

· [Individual items and how they are to be implemented.]

[Individual items and how they are to be implemented.]

[Individual items and how they are to be implemented.]

[Individual items and how they are to be implemented.]

SWOT Analysis (Strengths, Weaknesses, Opportunities, & Threats) Comment by Loran: Should be AT LEAST two things per CSF (S.W.O.T.). Please delete this comment BEFORE submitting assignment u01a1.

[General statement about the critical success factors (CSFs) that will make the project a success]

· Strengths: [What things is the organization very good at? Examples: well-trained staff, previous project management experience, leadership in the field.]

· Weaknesses [What things is the organization need improvement on? Examples: running over budget, talent skill sets not up to par, little or no project management experience.]

· Opportunities [What market forces is the organization taking advantage of? Examples: First to market, new technology, one of a kind.]

· Threats [What outside market forces are threats to the organization? Examples: A competitor developing the same product or service, new technology that is a “game changer”, does not comply with government mandates.]

Known Project Risks, Constraints, & Assumptions Comment by Loran: Known things about the project at the start. This is impacted by employees, stakeholders, and company policies and other things. Please delete this comment BEFORE submitting assignment u01a1

· Risks [What types of Risks are known at the beginning of this project?]

· Constraints [What resources (Human, materials, capital) are limited for this project?]

· Assumptions [What can we assume to be a standard part of this project?]

Roles and Responsibilities: [Description on the how the roles and responsibilities have been divided amongst the project team members.]

[GUIDANCE: Moving Towards Distinguished Performance on the Project Charter Comment by Loran: Delete this guidance and comment BEFORE submitting assignment u01a1.

· Project Overview (General background of the project.)

· Key Milestones (Examples: Key deliverables such as the design of a website or the coding behind the website.)

· Describes a changing marketplace that justifies the project. (If we don’t do it, our competition will!)

· Expansion on the roles and responsibilities of team members. (Name, role, responsibilities, delegation of authority etc.)

· Assigning authority to the project manager so she/he may expend organizational assets (human resources, money, equipment, software etc.)]

[OVERVIEW OF TEAM CONTRACT: Comment by Loran: Delete this OVERVIEW and comment BEFORE submitting assignment u01a1.

T

eam Contracts define how the team members interact with each other. In other words, these are the rules of engagement for the team. For larger size teams this document may become quite extensive in order to make sure everyone understands meeting etiquette so that the team meetings flow smoothly. Beyond the rules of a meeting it may show delegation of authority to Subject Matter Experts (SME) or group leaders who are responsible for a part of the project. Bear in mind that the project manager is ultimately responsible for the success or failure of a project.

This outlines the Project Manager’s expectations of the team members and may also include the Project Sponsor, the client or customer and other stakeholders who may be impacted or have a concern with the project’s deliverables.]

Team Member Signatures:

_______________________________________________________

Project Manager: [Enter Your Name Here]

_______________________________________________________

[Title: Name]

_______________________________________________________

[Title: Name]

_______________________________________________________

[Title: Name]

[GUIDANCE: Moving Towards Distinguished Performance on the Team Contract Comment by Loran: Delete this GUIDANCE and comment BEFORE submitting assignment u01a1.

Please add this additional information in the appropriate places in the body of the section above. Here are some additional things that may be added to the template to customize it or elaborate on information that is known about the project:

· Team Members Names AND Job Title AND Department/Area

· Code of Conduct (New Section)

· Collaboration Tools (New Section)

· Collaboration Skills (New Section)

· War Room (New Section)

· Separate Team Room for Project

· Features

· Availability

· Add an overview of the team goals

· Will there be any offsite meetings? If so, what are the rules?

· Is there a need for training?

· On a new tool?

· On new equipment?

· Certification?

· Are there sub groups or smaller teams feeding into the main project?

· Are there contractors? How do they fit into the team contract?

· What are the team rules when dealing with outside contacts?

· Clients?

· Vendors?

· Other Organizations?

· Adding additional information about each section in the document. (Example: Commitments and what that means within the context of the project.)]

[OVERVIEW OF PROJECT SCOPE Comment by Loran: Delete this OVERVIEW and comment BEFORE submitting assignment u02a1.

S

cope Statements succinctly define what exactly is going to be achieved in the project. They also define what is NOT going to be done as well. For example, a computer lab at a university may upgrade the operating system of the computers but will not be upgrading the machines. ]

Project Overview

GUIDANCE: Describe the background and context for the project and why it is being undertaken. Discuss the business value of the work being performed.

Project Scope

GUIDANCE: This section is where you clearly define the logical boundaries of your project. These statements are used to define what is within the boundaries of the project and what is outside those boundaries. Data, processes, applications, or business areas are items that could be examined. The following might be helpful to include: The types of deliverables that are in scope and out of scope (business requirements, current state assessment). The major life-cycle processes that are in and out of scope (analysis, design, testing). The types of data that are in and out of scope (financial, sales, employee). The data sources (or databases) that are in scope and out of scope (billing, general ledger, and payroll). The organizations that are in scope and out of scope (human resources, manufacturing, vendors). The major functionality that is in scope and out of scope (decision support, data entry, management reporting).

The scope of this project includes and excludes the following items:

In scope: Comment by Loran: Add more items as needed. Delete this comment before submitting assignment u02a1.

· Deliverable that will be performed in this project.

· Deliverable that will be performed in this project.

· Deliverable that will be performed in this project.

· Deliverable that will be performed in this project.

Examples: Click here to enter text.

Out of scope: Comment by Loran: Add more items as needed. Delete this comment before submitting assignment u02a1.

· Deliverable that will NOT be performed in this project.

· Deliverable that will NOT be performed in this project.

· Deliverable that will NOT be performed in this project.

· Deliverable that will NOT be performed in this project.

Examples: Click here to enter text.

[OVERVIEW OF WORK BREAKDOWN STRUCTURE Comment by Loran: Delete OVERVIEW and comment BEFORE submitting assignment u02a1.

A

Work Breakdown Structure (WBS) is included in the Scope Statement Documentation. Usually there are TWO views.

The first view is a hierarchical one that is usually worked upon by the project manager and team to discover exactly what tasks need to be done and in what order. (You will have to show more detail or levels than these examples.)

WBS Hierarchy Example (Created in Microsoft VISIO, saved as a jpeg picture, inserted into this Word document)]

The second view is a list view or outline of the WBS.

Project: Building a Garage

1.0 Initiate

1.1 Need a Garage?

1.2 Etc.

2.0 Plan

2.1 What Type of Garage?

2.2 Etc.

3.0 Execute

3.1 Pour the Foundation

3.2 Etc.

4.0 Monitor & Control

4.1 Observe the Cement Workers

4.2 Etc.

5.0 Close

5.1 Inspect Garage

5.2 Etc.

Note that the hierarchy view and the list view have the same tasks and are numbered the same.

The graphic view may be achieved by using MS VISIO, MS Word (Draw Feature), or MS PowerPoint Organization Template.

[GUIDANCE: Moving Towards Distinguished Performance on the Project Scope Comment by Loran: Delete this GUIDANCE and comment BEFORE submitting assignment u02a1.

· A thorough explanation of

· What is in Scope

· What is NOT in Scope

· Adding color to the WBS to further clarify a phase or layer

· Making sure the numbers match the tasks between the Hierarchy WBS and the List WBS.

· Project Deliverables also include project documentation (Team Contract, Project Charter, Scope Document, etc.)