Planning for Risk and Change Geoff Leese Sept 1999 revised Sept 2001, Jan 2003, Jan 2006, Jan 2007, Jan 2008, Dec 2008 (special thanks to Geoff Leese)

Slides:



Advertisements
Similar presentations
Chapter 7 Managing Risk.
Advertisements

© 2012 Jones et al: Strategic Managerial Accounting: Hospitality, Tourism & Events Applications 6thedition, Goodfellow Publishers Chapter 14 Capital Investment.
ICS 442 Software Project Management
Chapter 3 Program Management and Project Evaluation Professor Hossein Saiedian McGraw-Hill Education ISBN
1 Investment Appraisal Geoff Leese Sept 1999 revised Sept 2001, Jan 2003, Jan 2006, Jan 2007, Jan 2008, Dec 2008 (special thanks to Geoff Leese)
Chapter 9 Project Analysis Chapter Outline
Risk Analysis & Management. Phases Initial Risk Assessment Risk Analysis Risk Management and Mitigation.
Chapter 7: Managing Risk
Projmgmt-1/33 DePaul University Project Management I - Risk Management Instructor: David A. Lash.
Software Development Contracts and Legal Issues Cost plus Fixed price Combined.
Project Risk Management
Software project management (intro)
The Analyst as a Project Manager
Managing Project Risk.
FDM11 Capital investment apprasal 3 Capital investment appraisal 3.
PROJECT EVALUATION. Introduction Evaluation  comparing a proposed project with alternatives and deciding whether to proceed with it Normally carried.
Software Project Risk Management
Project Risk Management Risk Mitigation. Risk Management  The prime objective of risk management is to minimize the impact and probability of the occurrence.
Financial Analysis Fundamental
Don Cole Risk Assessment and Mitigation Project Management for ARA Engineers and Scientists.
Feasibility Study: Economic feasibility Technical feasibility
Project Risk Management
Introduction ► This slide deck provides a suggested framework for the financial evaluation of an investment project. When evaluating any such project,
Capital expenditure decisions: an introduction
Software Project Management
University of Sunderland CIFM02 Unit 3 COMM02 Project Evaluation Unit 3.
Chapter 10 Contemporary Project Management Kloppenborg
HIT241 - RISK MANAGEMENT Introduction
Managing Risk. Objectives  To Describe Risk Management concepts and techniques  To calculate and analyze a project using Probability of completion 
Risk Management - the process of identifying and controlling hazards to protect the force.  It’s five steps represent a logical thought process from.
Software Project Management 4th Edition
Software Project Management
Risk evaluation Risk evaluation is meant to decide whether to proceed with the project or not, and whether the project is meeting its objectives. Risk.
IB Business and Management
Managing Risks in Projects. Risk Concepts The Likelihood that some Problematical Event will Occur The Likelihood that some Problematical Event will Occur.
Quick Recap Monitoring and Controlling. Phases of Quality Assurance Acceptance sampling Process control Continuous improvement Inspection before/after.
© The McGraw-Hill Companies, Software Project Management 4th Edition Risk management Chapter 7.
Ch 4 - Learning Objectives Scope Management You should be able to: n Discuss the relationship between scope and project failure n Describe how strategic.
Managing Risk The Science and Art of IT Risk Assessment for Project Managers Presented at the FCW Events Government PM Summit November 2004 Michael Lisagor.
1 Risk Management 2 n IEEE defines risk as: “the likelihood of an event, hazard, threat or situation occurring and its undesirable consequences” [Std.
Question Four: Project Risk Management PMBOK definition of Project Risk Project risk management is the art and science of identifying, analyzing, and responding.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, Inc., All Rights Reserved. 1-1 McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, Inc., All Rights.
SOFTWARE PROJECT MANAGEMENT
Unit 5 Operations Management Location. Learning Objectives To be able to explain the causes and consequences of location and relocation – domestically.
Software Project Management Lecture 5 Software Project Risk Management.
Software Project Management
Risk Management. 7–2 Where We Are Now 7–3 Risk Management Process Risk –Uncertain or chance events that planning can not overcome or control. Risk Management.
Introduction to Project Management Chapter 9 Managing Project Risk
Project management Topic 5 Risk. What is risk? An uncertain outcome – either from a positive opportunity or negative threat Risk management is about:
University of Sunderland CIFM02 Unit 5 COMM02 Project Hazard Management and Contingency Planning Unit 5.
R i s k If you don’t attack risks, they will attack you.
Copyright 2012 John Wiley & Sons, Inc. Part II Project Planning.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
Accounting systems design & evaluation 9434SB 18 March 2002.
RISK MANAGEMENT PROCESS PREPARED BY: MUHAMMAD SULAIMAN
Project Management PTM721S
Project Evaluation and Programme Management
2017/18 SIP Request Process September 2016.
Project Management – PTM721S
Systems Analysis and Design in a Changing World, 4th Edition
Software Project Management
Initiating systems development
Recognization and management of RISK in educational projects
Software Project Management
Project Risk Management
Lecture # 4 Software Development Project Management
Part II Project Planning © 2012 John Wiley & Sons Inc.
Software Project Management (SPM)
Costing and Finance P R Upadhyay.
Presentation transcript:

Planning for Risk and Change Geoff Leese Sept 1999 revised Sept 2001, Jan 2003, Jan 2006, Jan 2007, Jan 2008, Dec 2008 (special thanks to Geoff Leese)

Risk and risk management n Much “risk management” focussed on Health and Safety risks these days n Topic is much bigger than that ä Business risk ä Security risk ä Business continuity

Introduction n Is it worth doing? ä Cost/benefit analysis n What might affect it if we go ahead? ä Risk management

Cost-benefit analysis (1) n Cashflow projection n Payback period ä Time taken to “break even” n Return on Investment (Accounting Rate of Return) ä average annual profit/total investment*100

Cost-benefit analysis (2) n Present value ä value in year t/(1+r) t ä “r” is discount rate as decimal value n Discount factor tables are available! n Net Present Value of a project (NPV) ä Sum of discounted values of all cashflows for that project

Assessment of risk “Risky” projects less likely to start. Apply “Risk premium” to discount rates for NPV

Expected Value Weighted average of all possible outcomes. A useful measure for comparing contracts!

Risk Profile Analysis n Sensitivity analysis ä Vary each factor (in turn) by + or - 5% ä Recalculate costs/benefits ä Indicates sensitivity of project to each factor ä Helps with risk assessment n Monte Carlo Method? (see Cotterill. & Hughes Chap 7)

Decision trees (1) Improve or replace machinery? Market will expand, or not expand? D Improve Replace Expansion No expansion NPV (£) -100,000 75, , ,

Decision trees (2) n Improve - ä (0.2*-100,000) +(0.8*75,000) ä =£25,600 n Replace ä (0.2*250,000) + (0.8*-50,000) ä =£10,000 n Therefore choose Improvement !

Project Evaluation n Evaluate on economic,strategic and technical grounds n Assess all costs & income over lifetime of project n Discount accordingly n Allow for uncertainty! n Evaluate expected outcomes and choose strategies

Risk management (1) n Estimation errors ä Use historical data and keep records! n Planning assumptions ä State, and be prepared to revise them! n Eventualities ä Identify, and deal with them!

Risk management (2) n Hazard identification n Risk analysis n Risk prioritisation n Risk reduction n Risk monitoring

Hazard identification n Contract Factors (is it special or different?) n Customer Factors n Staff Factors n Project Methods n Technology Factors n Changeover Factors n Supplier Factors n Environment Factors Consider for each phase or product!

Risk Analysis (1) n Risk Value = Likelihood * Impact n Impact expressed as monetary values? ä Likely to be difficult or impossible! n Likelihood AND impact expressed using “arbitrary scale “ (1-10) n Most likely - 10, least likely - 1 n Highest impact -10, lowest impact - 1

Risk Analysis (2)

Risk Prioritisation n Prioritise by risk value? n Consider ä Confidence in assessment ä Compound risks ä Number of risks ä Cost of action n Risk Reduction Leverage (RRL) ä = (RV(before) - RV(after))/risk reduction cost ä Use the same units!

Risk Reduction (1) n Hazard prevention n Likelihood reduction n Risk avoidance n Risk transfer n Contingency planning

Risk Reduction (2) n Personnel shortfalls ä get the best, job matching, early scheduling, personal development, team building n Unrealistic estimating ä multiple estimates, use of different techniques, standardisation of methods, use of historical data

Risk Monitoring n Assign INDIVIDUALS to monitor risks n Part of “change plan” n Use PERT techniques to assess potential effects of uncertainties on project schedule ä 3 way estimating ä Activity standard deviations ä Probability & “Z” values” (Cott. & Hughes)

Evaluation and Review n Projects should be reviewed on completion n The risk management plan should be reviewed at the end of the project. ä Risks were successfully foreseen? ä Contingencies were properly planned for? ä Lessons to be learnt? ä Improvements to be made? ä should be built into the risk management plan

Change Control Plan n Vital part of the project plan n Changes are almost inevitable Example: the client originally asked for sweetcorn on all sandwiches but now wants sweetcorn on tuna only. What changes will need to be made? n Project roles should include a Project Librarian, responsible for logging change requests and responses.

Controlling Change n Risk of “scope creep” n One big change? Lots of little ones? n Poorly documented changes make maintenance and enhancement difficult n May comprise the integrity of the design n May comprise the profitability and deliverability of the contract

Change Control Plan n Change Request (CRF) n Change Specification n Change Analysis n Costing & feasibility n Change decision (Change Control Board) n Change implementation & documentation

And the downside - n Perceived as bureaucratic, expensive & time-consuming n Likely to annoy users and may affect their relationship with the company. n Will definitely annoy production staff. n Restricts responsiveness to user needs n Emphasises costs and control rather than user needs

Summary n Project evaluation ä should we do it? ä How should we do it? n Risk management - ä what COULD happen if we do? ä How will we cope if it does? n Change control

Further Reading ä ä Link to BSI risk management Link to BSI risk management