Upload
jasper-dennis
View
230
Download
1
Tags:
Embed Size (px)
Citation preview
Project Risk Management
EECS811: IT Project ManagementPresenter: Gavaskar Ramanathan
2
Overview
• Agenda [1]– PMBOK discussion
• Agenda [2]Case Study #1– Project risk management methodology for small firmsCase Study #2– Driving agile architecting with cost and risk
3
Question
• What is risk ?– An uncertain event or condition which has negatively
impact project cost, time or scope.
• What is risk management?– Systematic process of identifying, analyzing and
responding to project risk.– It includes maximizing the probability and consequence of
positive events and minimizing the probability and consequence of adverse events.
4
Summary
5
Overview
6
Process Explanation
• What is risk management planning ?– Deciding how to approach and plan risk management.
• What is risk identification ?– Which risks might affect the project and document them.
• What is qualitative risk analysis ?– Accessing the impact and likelihood of identified risks.
• What is quantitative risk analysis ?– Aims to analyze numerically the probability of each risk
and the consequence on project objectives.
7
Process Explanation (Cont..)
• What is risk response planning ?– Developing options and determining actions to enhance
opportunities and reduce threads to project objectives.
• What is risk monitoring and control?– Keeping track of the identified risks and monitoring and
identifying new risks and ensuring the execution on risk plans and evaluation their effectiveness in reducing risk.
8
Risk Management Planning
9
Risk Identification
10
Qualitative Risk Analysis
11
Rating Impacts For A Risk
12
Probability – Impact Matrix
13
Quantitative Risk Analysis
14
Cost Estimates From Interview
15
Cost Risk Simulation
16
Decision Tree Analysis
17
Risk Response Planning
18
Risk Monitoring And Control
19
Agenda [2]
• Case Study #1– Project risk management methodology for small firms
• Case Study #2– Driving agile architecting with cost and risk
20
Project RMM For Small Firms
• Introduction • Literature review• New risk management methodology design– Identification methodology need and characteristics– New methodology phases and tools
• Discussion and methodology validation– Implementation phases– Result discussion
21
Project RMM For Small Firms
• Introduction • Literature review• New risk management methodology design– Identification methodology need and characteristics– New methodology phases and tools
• Discussion and methodology validation– Implementation phases– Result discussion
22
Project Risk Management Methodology For Small Firms
• SME ( Small And Medium Enterprises)• SMEs generate 66.7% of employment in European
Union, employing over 90 million people.
23
Project RMM For Small Firms
• Introduction– SMEs are companies with limited resources due to their
size.– Most of the time there are not using project management
in some cases due to ignorance or complexity.
• The aim of this paper is to present a project risk management methodology designed specifically for these situations
24
Investigation Phases
25
Project RMM For Small Firms
• Introduction • Literature review• New risk management methodology design– Identification methodology need and characteristics– New methodology phases and tools
• Discussion and methodology validation– Implementation phases– Result discussion
26
Literature Review
• SMEs challenge– Growth accomplished through challenges– Raising capital and size of the company– Seeking access to new technologies– Strong capacity of innovation, however lack the resource
to manage the innovation process.– Various standards such as APM, IPMA, ISO, PMBOK can be
used only to large firms not SMEs
27
Project RMM For Small Firms
• Introduction • Literature review• New risk management methodology design– Identification methodology need and characteristics– New methodology phases and tools
• Discussion and methodology validation– Implementation phases– Result discussion
28
Identify Methodology Need & Characteristics• First phase– Identify the difficulties that SME encounter when facing
new project (7 different companies analyzed) – To confirm the information obtained in this first analysis, a
boarder study was carried with consulting firm with another 72 SMEs
– 17 Micro (24%) & 24 Small (33%) & 31 Medium (43%)– Sectors: Equipment (31%), services (15%), construction
(13%) and automotive (10%)
29
Identify Methodology Need & Characteristics
30
First Phase - Conclusion
• Conclusion– SMEs overlooked the initial and final project phases.– Chosen project not matching with company Strategic point
of view.– Hardly paying attention to closing phase of the project.– Lesson learned and project results.
31
Project RMM For Small Firms
• Introduction • Literature review• New risk management methodology design– Identification methodology need and characteristics– New methodology phases and tools
• Discussion and methodology validation– Implementation phases– Result discussion
32
New Methodology Phase And Tools
• Proposal:– Risk assessment should be more qualitative than
quantitative.– Objectivity priorities the risks according to their potential
impact.– Clear documentation, periodic review of risks and their
status into dynamics of the company.– Risk checklist and strategies to mange common risks.
33
New Methodology Phase And Tools
34
New Methodology Phase And Tools
35
New Methodology Phase And Tools
• Project definition– Project environment analysis– Definition of project objectives– Identification of strategic risk with project
36
New Methodology Phase And Tools
• Project planning– Definition of risk management plan– Operational risk identification– Risk analysis and evaluation– Project risk communication– Closure and final project evaluation– Project result management– Lesson learned
37
Risk Classification Criteria
• The RPI index value is calculated with the following formula:
• RPI = I x P = (Ic x It X Is ) x P• where:– I Risk impact– Ic Cost impact– It Time impact– Is Scope impact– P Risk probability.
38
Phases & Activities & Techniques
39
Project RMM For Small Firms
• Introduction • Literature review• New risk management methodology design– Identification methodology need and characteristics– New methodology phases and tools
• Discussion and methodology validation– Implementation phases– Result discussion
40
Implementation Phases
41
Result Discussion
42
Conclusion
• Less time spent on use of this methodology(< 85h) which is 3.77% of project time
• For shorter projects this % is increases because definition & planning and lesson learned and results management are the most time consuming and independent of project duration.
• Helps not only risk management, also other project management areas.
• Elimination of strategic risks and the correct definition of objectives, eliminating serious shortcomings in the project definition.
43
Agenda [2]
• Case study#1– Project risk management methodology for small firms
• Case study#2– Driving agile architecting with cost and risk
44
Question
• Does agility and architecture can coexist ?– We see agile methods that included architecting such as
scaled agile framework.– Five pieces of advice can help architects become more
effective in an agile world without having to implement new methods or frameworks.
45
Five Ideas
• Decision are your main deliverables • Keep a backlog of architectural concerns• Let economic impact determine your focus• Keep it small• Just enough anticipation.
46
Decision are your main deliverables
47
Keep a backlog of architectural concerns
48
Five Ideas
• Decision are your main deliverables • Keep a backlog of architectural concerns• Let economic impact determine your focus• Keep it small• Just enough anticipation.
49
References
• PMI—Project Management Institute, 2008. A Guide to the Project Management Body of Knowledge (PMBOK), 4th edition. Project Management Institute, Inc., USA.
• Sara Marcelino-Sadaba, Amaya Perez-Ezcurdia, Angel M. Echeverría Lazcano, Pedro Villanueva, 2013,Project risk management methodology for small firms”, International journal of project management, 32(2), pp.327- 340
• Poort, E.R. , 2014, Driving Agile Architecting with Cost and Risk, “IEEE Computer Society”, 31(5), pp.20-23