Presentation is loading. Please wait.

Presentation is loading. Please wait.

Project Management April 28, 2008 Eric Verzuh Project Management April 28, 2008 Eric Verzuh.

Similar presentations


Presentation on theme: "Project Management April 28, 2008 Eric Verzuh Project Management April 28, 2008 Eric Verzuh."— Presentation transcript:

1 Project Management April 28, 2008 Eric Verzuh Project Management April 28, 2008 Eric Verzuh

2 Project Manager clearly assigned Know the stakeholders Communication Plan & RACI Define the goals and constraints Statement of Work and Charter Project Manager clearly assigned Know the stakeholders Communication Plan & RACI Define the goals and constraints Statement of Work and Charter

3 Proposals vs. Project Mgt  Proposal – what will be accomplished.  Full lifecycle focus  Final results  Stakeholders are widely defined  Project Plan – how it will be accomplished.  Focus on the change activities.  Project ends before results are achieved.  Primary stakeholders are actively involved in creating change.

4 Identify Stakeholders! Who cares? What do they care about? How do I find them?

5 Identify Stakeholders! Primary Actively involved Allies Opponents Secondary Affected by the project Could become a primary if requirements are not met

6 Stakeholder Analysis Form  Worksheets provide a basis for consistency  Twenty downloadable forms  Use and modify them  www.versatilecompany.com/forms Fast Foundation in Project Management

7 Project Workshop  Name your stakeholders  Be specific when possible 15 minutes

8 Responsibility Matrix (RACI) E – Responsible for driving execution A – Final approval for decisions C – Must be consulted I – Must be informed

9 Plan Communication  Who needs information?  What information do they need?  When do they need it?  How will you get it to them?  How will you know they received it? Projects do not fail from over communication!

10 Statement of Work  Purpose  Scope Statement  Deliverables  Objectives  Cost & Schedule Estimates  Organization Structure  Monitoring & Control Processes  Risks  Project Specific Issues Minimum Content Terminology Check: Charter or SOW or Scope Statement?

11 Create a detailed action plan Assign responsibilities Assess the overall resource requirements Create a detailed action plan Assign responsibilities Assess the overall resource requirements

12 Benefits of Planning Planning is always valuable. The time invested in planning represents an investment in better performance. “In preparing for battle I have always found that plans are useless, but planning is indispensable.” Dwight D. Eisenhower

13 A Planning Method Publish Plan

14 A Planning Method Publish Plan

15 Work Breakdown Structure Project Tier 1 Tier 2 Tier n

16 Work Breakdown Structure Detailed tasks are the basis for planning Tier 1 Tier 2 Project Tier n

17 WBS Landscape Project

18 WBS Guidelines Completion criteria – what it means to be ‘done’. Summary tasks Work packages Project

19 1.Top-down decomposition 2.Work packages add up to their summary task 3.Task name = An activity that produces a product 4.Size guidelines: 1.8/80 2.Reporting period 3.If it is useful for managing WBS Guidelines Summary task Work package Completion criteria – what it means to be ‘done’

20 WBS Exercise  What are the major products or activities?  Use strong task names!  Sequence does not matter on the WBS.

21 Project Workshop  Make a WBS  Focus on Tier 1 – get approval from Eric 20 minutes Use ‘WBS Pads’ on flip charts

22 Review Questions  Teams of 3: Write 3 “quiz” questions about risk management  Pick key topics – something that struck you as particularly valuable  5 minutes

23 Risk Management

24 Risk Log Contingency & Reserve Risk Management Plan

25 More questions…  What’s wrong with this risk description:  “The project has physical security risks.”  What sources of probability do we have?  What is the difference between a risk profile and a risk log?  Give an example of a “trigger point”

26 Class Project: Risk Log  Use the risk log found in FFMBA  Top seven risks  Sit as a team for the rest of today’s class

27

28 Risk Identification - Threats  What could cause your project to fail?  They aren’t a problem yet – but they could be…  Be specific – the more specific the better  Threats can come from outside the project

29 Risk Identification - Risk Profile  What surprises have hurt you in the past?  How will you know about them before they hurt you again?  Project team?  Customer environment?  Technical challenges?

30 Prioritize Risks Page 98 Impact Probability

31 Risk Analysis  Condition (Describe the threat)  Consequence (Impact)  Probability  Response Strategy Page 94

32

33 Project Workshop  Workshop projects:  A project you understand well  3-6 months long  3-10 person team  Project NameYour Name  Brief Description

34 Risk Management


Download ppt "Project Management April 28, 2008 Eric Verzuh Project Management April 28, 2008 Eric Verzuh."

Similar presentations


Ads by Google