1. Project Risk Management For IT Professionals António Vieira Manager, Viatecla SA III Encontro Da Comunidade SQLPORT Lx, 2010-07-13

2. 1. The problem

3. Maybe you’ve heard one or two of this…. I did everything right but this was just unexpected… It’s not our fault, they didn’t deliver the servers on the agreed schedule. Ops, the restore is not working… We just lost very important data! We are delayed because I got unskilled team members and I assumed top level programmers.

4. In the News…

5. What have we did about this before it happened?

6. 2. What is a Risk?

7. “Project risk is an uncertain event or condition that, if occurs, has a positive or a negative effect on a project objective.”

8. Uncertain: the event might occur with a determinate probability and impact Positive or a negative: if the event occurs it can have a positive or negative impact on the project Project objective: the impact is measured on the project objectives

9. probability: the risk probability measures the level of uncertainty over the occurrence of the risk. impact: the risk impact measures the degree that it affects one or more project objectives Probabiliy x Impact: the overall value for the risk. Can be measured in money (Expected Monetary Value)

10. Impact can be over one of the 4 types of project concurrent objectives (Triple-Constraint) Project ScopeCostQualityTime

11. 3. Risk Management

12. “Risk Management is the systematic process of identifying, analyzing, and responding to project risk” Goals on Risk Management: – Maximize the probability and impact of positive events – Minimize the probability and impact of negative events – Give confidence and control of the risk tolerances of Stakeholders

13. Steps In Risk Management Identify Risks Get insight on risks Plan Responses to risks Control Risks

14. PMI steps in Risk Management Plan Risk Management Identify Risks Perform Qualitative Risk Analysis Perform Quantitative Risk Analysis Plan Risk Responses Monitor & Control Risks Planning Monitoring & Control

15. Risks are planned.

16. Threats Response Strategies Avoid: Change the project plan in a way the risk does not longer exists (probability or impact) Transfer, Deflect or Allocate: Decision to transfer the responsibility for the risk impact and management to an external entity (insure, subcontract) Mitigate: Include changes to the plan that reduce the probability and/or impact of the risk. Accept : Project plan is not changed. A contingency allowance is added as reserve to the project. – Passive Acceptance: No plan is developed. A workaround will be implemented if the risk is triggered. – Active Acceptance: A contingency plan is developed to implement when the risk is triggered. A fallback plan can be implemented as a backup of the contingency plan.

17. Risk Register

18. Opportunities Response Strategies Exploit: Remove the uncertainty on this opportunity. Share: Decision to transfer the responsibility for the risk impact and management to an external entity that might get greater benefits. Enhance: Include changes to the plan that increase the probability and/or impact of the risk. Accept : Project plan is not changed.

19. 4. Risk Attitude

20. Risk Management is not work of the PM.

21. An example in SQL code

22. 1 Assumption = 1 risk

23. Thank you. Questions?

24. 5. Risks & Schedule

25. How to account for uncertainty in schedule?

26. Add Reserve Per Task

27. Phase / Project Reserve

28. Parkinson’s Law: Work expands so as to fill the time available for its completion.

29. Monte Carlo Analysis

30. Monte Carlo Analysis and Schedule Confidence