Risk Management Overview

1. Risk Management Overview Week 2

2. Review of Project Life Cycle Phases PMBOK® p. 41

3. Project Risk • “A project risk is an uncertain event or condition that, if it occurs, has a positive or negative effect on at least one of the project’s objectives” • Threat risk has a negative impact on the project’s objective(s). • Opportunity risk has a positive impact on the project’s objective(s) such as allowing the project to finish early, with less cost, and with more scope (functionality) than originally planned. PMBOK® p. 238

4. Project Risk Management • “Project risk management includes the processes concerned with conducting risk management planning, identification, analysis, responses, and monitoring and control on a project; most of these processes are updated throughout the project. ” PMBOK® p. 237

5. Project Risk Management Objective • “The objectives of Project Risk Management are to increase the probability and impact of positive events, and decrease the probability and impact of events adverse to the project.” PMBOK® p. 237

6. Risk Management Areas PMBOK® p. 239

7. Risk Management Areas PMBOK® p. 340

8. Knowledge Areas – Risk Centered Adapted from Wideman, 1992

9. Project Life Cycle and Risk Management When is risk management performed? Risk Management Planning Risk Management Planning Risk Identification Qualitative Risk Analysis Quantitative Risk Analysis Risk Response Planning Risk Monitor/Control Iterate risk identification, analysis and response planning Risk lessons learned

10. Stakeholders • “individuals and organizations that are actively involved in the project, or whose interests may be affected as a result of project execution or project completion. They may also exert influence over the project’s objectives and outcomes” PMBOK® p. 24

11. Risk Stakeholders PMBOK® p. 26

12. Risk Tolerance • Propensity (individual or organization) to operate in an uncertain environment. • Risk… • Seeker – embraces risk to realize gains • Tolerant – tolerates risk to ensure success • Averse – avoids risk to avoid failure http://articles.techrepublic.com.com/5100-10878_11-6035405.html http://articles.directorym.net/Know_Your_Risk_Tolerance_First-a881332.html

13. Risk tolerance may change throughout the project depending on problems, crises, regulatory changes, and changes in stakeholders.

14. Which trait(s) describe your style? • Taking risks makes good sense only in the absence of acceptable alternatives. • I generally prefer stimulation over security • I have confidence in my ability to recover from my mistakes, no matter how big. • I believe opportunity generally knocks only once. • It is better to ask for permission than to beg for forgiveness. • Success in management is as much as a matter of luck as ability. • I can handle big losses and disappointment with little difficulty • Given a choice, I would choose a $3,000 annual raise over a $10,000 bonus that I have a one-in-three chance of winning. • I am willing to try anything once. • I seek adventure. • I stick to the rules.

15. Risk Tolerance Game Successful project management is spotting the projects that will succeed and shouting "mine" and for the rest ducking and shouting "yours". http://www.project-training-uk.freeserve.co.uk/page2.htm

16. The Cost of Uncertainty • Uncertainty decreases as the project progresses • The cost (amount at stake) of making changes (to address risks) increases as the project progresses • Addressing risks later in the project is more expensive than earlier action • Goal is to reduce uncertainty early in the project by effective risk management

17. Risk Management Should be Adapted Based on • Project size, importance, and complexity • Risk tolerance (organizational and stakeholders) • Organizational policies and culture • External regulatory environment • There is no “one size fits all” in project risk management

18. Risk Management Implementation • Resistance to risk management • Some companies want to avoid talking about risks • Tendency to deal with risks when they occur • Fear that talking about a risk will make it happen • Requires commitment, discipline and participation • Many companies stop after identifying and qualifying risks instead of integrating all risk processes into the entire project life cycle.

19. Risk Management Excuses A lack of planning by you does not constitute an emergency for me. http://www.project-training-uk.freeserve.co.uk/page2.htm

20. Risk Management Planning Planning without action is futile, action without planning is fatal. http://www.project-training-uk.freeserve.co.uk/page1.htm

21. Risk Management Processes PMBOK® p. 239

22. “Risk Management Planning is the process of deciding how to approach and conduct the risk management activities for a project” The risk management plan is a subset of your overall project plan and should be completed early during project planning PMBOK® p. 242

23. Risk Management Planning PMBOK® p. 242

24. Risk Management Planning • Set overall goals and objectives • Determine tolerance level • Decide how much money, time, and other resources will need to be allocated for risk management activities • Establish templates, checklists, and other tools to be used in risk management for your project • Create probably and impact scales • Establish importance of risk management • Decide basis for evaluating project risk PMBOK® p.243 - 246

25. Risk Planning Inputs • Project Management Plan • Project Charter • Project Scope • Stakeholder risk tolerance • Used as an input for defining impact scales • Determines formality of your risk plan and processes • Factored in to developing risk responses • May differ from project manager and/or team risk tolerance • Risk management plan template

26. What do you do if.. • Your customer is not a risk taker, but you (the project manager) believes some risk will always be present and needs to be managed? • You (the project manager) thinks the customer is wanting to take too many risks?

27. Risk Management Planning Outputs • Risk management plan • Probably and impact scales • Changes/updates to the project management plan

28. Define Probability and Impact • Define significant ranges for probability scores • Define impact definitions for each of the 4 competing demands • Scope, time, cost, quality • Base these definitions on: • Historical data • Expert judgment • Risk tolerance • Organizational culture/policies

29. Probability Score Example (red) (red) (yellow) (green) (green)

30. Scope Impact Example (red) (red) (yellow) (green) (green)

31. Time Impact Example (red) (red) (yellow) (green) (green)

32. Cost Impact Example (red) (red) (yellow) (green) (green)

33. Cost Impact Example (red) (red) (yellow) (green) (green)

34. Quality Impact Example (red) (red) (yellow) (green) (green)

35. Create Probability and Impact Scales Some things that don't count are counted, many things that count aren't counted. http://www.project-training-uk.freeserve.co.uk/page1.htm

36. Tailor Risk Management to Your Project • Do we need a risk management officer? • Do we advisors or risk experts from outside the project? • Do we need a formal quantitative risk assessment? • How often do we need formal risk meetings? • Risk management processes are determined by the size, complexity, and organizational impact of the project.

37. The Risk Management Plan (RMP) • The RMP does not address individual risks • The RMP does address the processes for how risks will be identified, analyzed, responded to, and monitored throughout the project life cycle. • Include risk management activities in the project WBS, schedule, and budget. • Establish risk objectives for the team. • Risk communication plan. • How frequently will risks be addressed.

38. Create a Risk Management Plan People make a plan work, a plan alone seldom makes people work (Confucius).

39. Project Charter Example Table 5-2 Schwalbe, 2007 p. 185

40. Project Charter Example Schwalbe, 2006 pp. 86 - 87

41. Project Charter Example Schwalbe, 2006 pp. 86 - 87

42. Project Scope Statement Schwalbe, 2007 p. 187

43. Sample Scope Management Plan Example Schwalbe, 2007 p.184

44. Work Breakdown Structure (WBS) Example Schwalbe, 2006 p. 185

45. Work Breakdown Structure (WBS) Example Schwalbe, 2006 p. 176

46. Work Breakdown Structure (WBS) Example – Tabular Format 1.0 Concept 1.1 Evaluate current systems 1.2 Define Requirements 1.2.1 Define user requirements 1.2.2 Define content requirements 1.2.3 Define system requirements 1.2.4 Define server owner requirements 1.3 Define specific functionality 1.4 Define risks and risk management approach 1.5 Develop project plan 1.6 Brief Web development team 2.0 Web Site Design 3.0 Web Site Development 4.0 Roll Out 5.0 Support Schwalbe, 2006 p. 177

47. Project Schedule Example – Gantt Chart Schwalbe, 2006 p. 179

48. Project Cost Budget Estimates Example Schwalbe, 2006 presentation slide

49. Return on Investment Example Schwalbe, 2006 p. 126

50. Stakeholder Analysis Example Schwalbe, 2006