Project Overview

Final Project Due: April 29th by 5PM Does not need to include progress reports Each document is graded on a 2, 1, 0 scale Continuity, grammar, spelling…MATTER

Documents to be included: Problem statement Change Management Plan* Project Charter Communications Plan* Scope document Quality Management Plan* Organization Chart Risk Management Plan* RACI Chart Project closeout documents / post mortem (status report, lessons learned, etc) Stakeholder Register* Schedule / WBS Budget

**Every Plan must have a document Change Risk Communications Stakeholder Quality These documents have other items [stakeholder register, etc]. BUT every one of these need to have a document “management” plan as an introduction.

Problem statement What is it? What does it include/not include? Fist step in defining your project! Identifying the problem…. PM needs to tease out the real problem from the project’s sponsor, customer and other stakeholders Needs to be a clear concise description of the issue(s) that are being addressed by the project Basically answering the question why? A problem statement should not include solutions!

What is a “project charter” and what are the typical elements? Project Press Release ! Project name Sponsor Project manager Team members Purpose / initial scope / high level cost estimate Initial Timeline / Milestones Sponsor’s official commitment to the project

What is “project scope” and “scope statement” ? Web research Project Scope : part of project planning that involves determining and documenting a list of specific project goals, deliverables, tasks, costs and deadlines : what are we going to do? Scope statement : document what is and isn't included in the project scope

Org Chart example

Change management plan : Communication plan : Who needs to know? Ex: who should receive the list of pending change requests What do they need to know? Depending on the roles, some will receive details, others high level summary status When do they need to know? (frequency) Every week, every other week, once a month… which day of the week How should they receive it? Email, hard copy, collaborative websites (ex : sharepoint) Change management plan : how people submit changes? who reviews them? the steps for approving them? and how you incorporate into your plan Quality management plan : It starts with a project’s quality objectives. Then for each objective you define how you plan to achieve those quality levels which is called quality assurance. Finally you describe how you plan to monitor and measure quality performance whitch is called quality control.

Risk Management plan : It starts with identifying what could go wrong (i.e. risks). Then you analyze those risks and decide what you will do if they actually happen. 1) Identify risk: Are there uncertainties? Ex : key resources availability Are you choice limited ? Ex : a single vendor for key parts Are constraints significant? Ex: tight budget, fixed end date What level of experience do people have? Does the project depend on factors out of your control? Ex: politics 2) Assessing risk : assess impact (H/M/L), assess probability (H/M/L) – see example of table/graph on p39 3) Planning risk response (accept, avoid, control the pain ie risk mitigation, give the risk to someone else, give yourself options ie plan for contingency funds) 4) Track risk with a risk log (summary of the risk, planned response, who is handling/monitoring, results)