Project management
<Project Name>
Project Management Plan
<Course Number and Name>
Prepared By
<Names>
<Date>Table of Contents
1.Executive Summary 4
2.Introduction 4
2.1Description of Project 4
2.2Project Purpose or Justification 4
2.3Objectives 4
2.3.1Primary Business Objectives 4
2.3.2Project Objectives 5
2.3.3Benefits 5
2.4Project Success Criteria (Chapter 1) 5
2.5High Level Requirements (Chapter 5) 5
3.C hange Management (Chapter 4) 6
3.1Project Change Control Narrative: 6
3.2Project Change Control Flowchart: 6
3.3Project Change Request Form Template: 6
3.4Project Change Log Template: 6
4.SCOPE Description (chapter 5) 6
5.HiGH Level Work Breakdown Structure, Milstone Schedule and Project Boundaries 6
5.1Work Breakdown Structure 7
5.2Summary Milestone Schedule (Chapter 6) 7
5.3Project Exclusions 7
5.4Assumptions (Chapter 5) 7
5.5Constraints (Chapter 5) 7
5.5.1Solution Constraints 7
5.5.2Process Constraints 7
5.6Product Deliverables & Acceptance Criteria (Chapter 5) 7
6.PROJECT SCHEDULE (Chapter 6) 9
7.Summary High Level Budget (Chapter 7) 9
8.Quality Management Plan (Chapter 8) 11
8.1Quality Assurance: 11
8.2Quality Control: 11
9.Project Organization & Resources (Chapter 9) 12
9.1Internal Team Structure 12
9.1.1Narrative: Describe the internal team structure of the project, as well as how the project relates to the rest of the organization. Explain the logic/rationale behind why you think your proposed team structure is best for your project. 12
9.1.2Team Organization Chart: Include a chart that shows the details of how your very specific project team is organized/structured. 12
9.2Project Organization: Major Project Roles & Responsibilities: 12
9.3Project Team Members: External Interfaces: 13
9.4RACI Chart 13
9.5Equipment and Training Needs (Chapter 9) 13
9.5.1Equipment: Identify equipment, supplies, etc. that will need to be purchased to support your project team members – items your team members will need to complete their project assignments. 13
9.5.2Training: Identify what kind of training your team members must receive to perform well as team members and/or complete their project assignments. 13
10.Communications Plan (Chapter 10) 15
10.1Stakeholder communications requirements 15
10.2Escalation procedures (for resolving issues) 15
10.3Revision procedures (for updating the plan) 15
10.4Status Report Format 15
11.PROJECT RISK MANAGEMENT (chapter 11) 16
11.1 Detailed Risk Register 16
12.Procurement management Plan (chapter 12) 17
12.1Make/Buy/Lease analysis and Procurement Needs 17
12.2Procurement Source Selection Process 17
12.2.1Evaluation Criteria and Long List 17
12.2.2Short List 17
12.2.3Source Selection 17
12.3Vendor Performance Management and Closeout 17
13.STAKEHOLDER ANALYSIS (chapter 13) 18
13.1Stakeholder Register with Roles and Responsibilities 18
13.2Stakeholder Analysis 18
14.Monitoring & Control Procedures (Chapters 5-7) 19
15.Closeout CRITERIA 19
- Executive Summary
Briefly describe a profile of the Organization, Company or Site for which the project is being undertaken.
Provide a general overview of the project. Important background information and key points developed in the steps leading up to the project plan are included in this narrative. The summary should highlight the approach that will be taken in the implementation of the project and any factors that the leadership team has determined are important in the further development of the project plan. All the information in the following sections of the plan will support the information contained in this Executive Summary.
- Introduction
- Description of Project
A narrative description of what the project entails and how the project will be implemented. Can include the business drivers for taking on the project and the chief systems impacted.
- Project Purpose or Justification
- Objectives
- Primary Business Objectives
Bulleted statements of the measurable Business Objectives your proposed project will help achieve (Your project should support the achievement of business objectives)
Reference No. | Business Objective Description | Specific Goal |
- Project Objectives
Provide brief statements of the Project Objectives that will be achieved in the project. There may be numerous Project Objectives to support each Business Objective. These objective statements should be stated in terms that are specific and quantifiable.
Business Objective Ref. No. | Project Objective Ref. No. | Project Objective Description |
- Benefits
List bulleted statements of the benefits to be achieved by successful completion of the project. These statements can relate to tangible and intangible business goals, strategic goals, or core processes. They can indicate who will benefit and how the benefits may be seen.
- Project Success Criteria (Chapter 1)
Identify measurable criteria that define success for the concept.
- High Level Requirements (Chapter 5)
This section will list the high level Requirements that have been identified to date. These requirements should be related to a Business or Project Objective and identified as such through inclusion of that requirements reference number.
Objective Ref. No. | Requirement Ref. No. | Requirement Description |
- C hange Management (Chapter 4)
For this assignment you will be designing the processes and some of the key forms you will use to manage requested and actual changes to your project. Every change that enters your project should pass through a formal documented change control process. The change control system is a collection of processes that allow change requests to be analyzed (examined to determine their impact on the project baselines), approved, declined, and subsequently managed.
Include a change management process narrative, flowchart, Change Request Form and Change Log
- Project Change Control Narrative:
- Project Change Control Flowchart:
- Project Change Request Form Template:
- Project Change Log Template:
- SCOPE Description (chapter 5)
This section will identify the work envisioned to complete this project and achieve the stated Project Objectives. These statements will be bulleted out and indicate reference to affected systems or specific measurable standards.
- HiGH Level Work Breakdown Structure, Milstone Schedule and Project Boundaries
Include all aspects of the project, including project management, support functions, quality assurance, configuration management, and subcontracted work
- Work Breakdown Structure
Insert a high level WBS that can be further decomposed by the team into additional work packages and activities for scheduling. Include both product and project management deliverables.
- Summary Milestone Schedule (Chapter 6)
A list of the key milestones anticipated along with a completion date.
- Project Exclusions
It is important to not only list the work that will be done but to also be very clear on what will not be done in this project. By stating exclusions, the project team will reduce the risk that scope creep will occur later.
- Assumptions (Chapter 5)
Presupposed facts or conditions upon which the Project Team has relied in order to complete this Project Plan. List out in a bulleted format.
- Constraints (Chapter 5)
List in bulleted format the limitations that will be in effect during the course of the project. These constraints may be broken out by Solution and Process categories. Any other constraints that do not fit into these categories should be listed separately.
- Solution Constraints
Factors or decisions that have been made that will limit or influence the project and decisions that will be made throughout the implementation.
- Process Constraints
Limitations related to business process changes that must be considered during implementation. Include limitations as they relate to time or training required until the business is ready to use the new process.
- Product Deliverables & Acceptance Criteria (Chapter 5)
List the key tangible product outputs (deliverables or services) to be provided by this project. Explain the criteria that will be used by the product users to determine if the project can be accepted. It may be useful to portray these in a table.
Deliverables | Date Available | Acceptance Criteria |
Table x. Key Project Deliverables
- PROJECT SCHEDULE (Chapter 6)
Complete first draft project schedule. The schedule you complete this week is to include MORE DETAILS (go to lower level) than the schedule/deliverables you provided last week for Unit #5. You are developing your project SCHEDULE -- the second of three elements in the triple constraint! This is the only focus for this week's assignment so it should be DETAILED -- see Schwalbe Chapter 06 for the processes included in this key knowledge area. Please include a brief narrative that addresses the key time management concepts that you used to develop your schedule for your specific project such as: identifying/sequencing activities, durations, estimating activity resources, critical path, etc. Include both product and project management deliverables.
- Summary High Level Budget (Chapter 7)
Identification of the key budget items with estimated costs that have been identified to date. This information can be laid out in a table and identified in terms of months or years as appropriate. (Create your own budget matrix)
Budgeted Item | Time Period 01 | Time Period 02 | Time Period 03 | Time Period 04 | Total |
Time Period Total | |||||
Accumulating Total |
- Quality Management Plan (Chapter 8)
Without proactive quality planning there is an increased risk that key stakeholders will not be satisfied with project deliverables. For this assignment, you will plan for Quality Assurance and Quality Control. You will define the quality standards the project must meet to be successful – and address how those standards will be measured / confirmed. Quality Control and Quality Assurance are highly interdependent. Quality Assurance is done to verify you have designed the right processes and are executing those processes well. Quality Control is done to verify that the actual results of your processes (deliverables) meet requirements/expectations.
- Quality Assurance:
Quality Assurance focuses on Project Processes. Think of quality assurance as activities that help to prevent quality problems while developing project deliverables. Quality assurance ensures that your project processes are appropriate and consistently followed. | |||
Project Process/Procedure Subject to Quality Assurance (Activities you will use to help avoid the need for rework) | Quality Standards for Process / Procedure1 | Quality Assurance Activity and Frequency2 (Audits, Process Reviews, Process Analysis, Assessments, etc.) | Who is Responsible for performing Assurance Activity and reporting results |
1Stakehlder’s standards /expectations for the processes
2 Activity that will be performed to monitor if project processes /procedures are being followed and standards / expectations are being met
- Quality Control:
Quality Control focuses on Project Deliverables. Quality control is a set of activities designed to evaluate project deliverables. Quality control focuses on finding defects in deliverables / verifying that requirements are being achieved. | ||||
Deliverable Name/Description | Metric (Attribute that will be measured) | Physical or Performance Quality Standard1 | Quality Measurement Activity and Frequency2 | Who is Responsible for performing Control Activity and reporting results |
1Actual value or range of values/criteria that must be achieved to meet quality standards /customer satisfaction
2How the quality metrics measurements will be taken. Describe the specific activity that will be used to conduct measurement and determine if the deliverable is in compliance with quality standards
- Project Organization & Resources (Chapter 9)
For this assignment, considering your project tasks, dependencies, and project schedule, you will complete some critical components of a Project Human Resource Plan. Great teams develop as a result of careful planning. Successful plans take into consideration needed team member’s expertise, skills, ability to learn, as well as ability to work with others. Team member availability is also a very critical factor.
- Internal Team Structure
- Narrative: Describe the internal team structure of the project, as well as how the project relates to the rest of the organization. Explain the logic/rationale behind why you think your proposed team structure is best for your project.
- Internal Team Structure
- Team Organization Chart: Include a chart that shows the details of how your very specific project team is organized/structured.
- Project Organization: Major Project Roles & Responsibilities:
Identify the individuals performing the project's primary/main roles & responsibilities. This can be used to establish accountabilities throughout the project’s lifecycle | ||
Major Role / Function1 | Major Responsibilities | Name and Title (May be multiple names per Major Role) |
1Examples (Not exhaustive): Steering Committee, Executive Sponsor, Program Manager, Project Manager, Technical Lead, Testing Lead, Training Coordinators, Developers, Testers, Specialists: (Architecture, Security, MIS, etc.),
- Project Team Members: External Interfaces:
Identify project personnel who are charged with establishing/maintaining key relationships with people /organizations outside the project team. This can be used to establish accountabilities throughout the project’s lifecycle | |
Team Member Name and Title | External Organization / Entity for which Team Member is the Primary Interface / Liaison |
- RACI Chart
Construct a RACI chart to clarify at a detailed level the relationship between project work and the people doing the work. The RACI chart for your project must show the four key roles your project stakeholders will perform when completing the individual project work items:
Responsible role (R) – Identify who is responsible for doing the work. - Who is assigned to and will perform the work?
Accountable role (A) – Identify who has final decision and 'ownership' of the work. Who has the authority to sign off for the work?
Consulted role (C) – Identify the subject matter experts that have the information needed to complete the work. Whose input is needed before decisions are made or work begins?
Informed role (I) – Identify who needs to be updated on the progress of the work (after decisions/actions are taken)? Whose work depends on this deliverable?
- Equipment and Training Needs (Chapter 9)
- Equipment: Identify equipment, supplies, etc. that will need to be purchased to support your project team members – items your team members will need to complete their project assignments.
- Equipment and Training Needs (Chapter 9)
- Training: Identify what kind of training your team members must receive to perform well as team members and/or complete their project assignments.
- Communications Plan (Chapter 10)
The communication plan guides project communications and includes the following sections.
- Stakeholder communications requirements
(What information will be communicated, including format, content, and level of detail)
Communications Table / Matrix Example (complete your own)
Communication Item | Frequency of Communication | Format/ Media/ Distribution Channel | Content Author(s) | Reviewer(s) Approver(s) (sign-off before distribution | Audience/ Recipients (Stakeholders who will use the communication items) | Feedback Mechanism |
- Escalation procedures (for resolving issues)
- Revision procedures (for updating the plan)
- Status Report Format
- PROJECT RISK MANAGEMENT (chapter 11)
Use this table to identify at least five sources of Project Risk (RBS Level one). The risk sources/categories must not be the risks themselves - but categories within which the true risks will fit. Ensure your completed list is consistent with the scope of your specific project. .
Sources of Project Risk: Risk Category |
.
11.1 Detailed Risk RegisterRecreate the following table in excel and attach it to the end of this document
- Procurement management Plan (chapter 12)
- Make/Buy/Lease analysis and Procurement Needs
Describe Items or Services essential for project success that could be Made, Purchased or Leased. | ||||||
Item or Service to be Procured | Description / Technical Information | Why is item / Service Needed | Make Buy Lease | Type of Contract | Need By Date | Purchase Approval Authority |
- Procurement Source Selection Process
- Evaluation Criteria and Long List
- Procurement Source Selection Process
- Short List
- Source Selection
- Vendor Performance Management and Closeout
- STAKEHOLDER ANALYSIS (chapter 13)
- Stakeholder Register with Roles and Responsibilities
Identify and state responsibilities assigned to each major role in the project, and identify the individuals who are responsible for those functions and activities. A table of may be the best way to depict these.
Stakeholder Name | Organization | Role/Position (in Current Organization) | Key Project Roles and Responsibilities |
Internal - Identified by Functional Area or resource group and with a description of responsibilities. External - Identified by Vendor or outsource group and with a description of responsibilities.
- Stakeholder Analysis
Include Name, Power/Interest, Current & Desired Engagement and Stakeholder Management Strategies
Name | Power / Interest | Current Engagement Level | Desired Engagement Level | Stakeholder Management Strategy |
- Monitoring & Control Procedures (Chapters 5-7)
A narrative of the way in which the project will be monitored to ensure that all requirements are met and what control procedures will be used to correct deficiencies. At a high level this narrative may also include a description of who will be responsible for analyzing this data and who will communicate this data to the sponsor.
- Closeout CRITERIA
List those activities that must occur to close the project once the final product deliverables have been accepted by the user as specified in section 5.6.
19
cd4ivro0o8
V1.0