Defence Project Management 2007 Learning to love project risk management Dr Andrew Tyler DG Ships, DE&S.

Slides:



Advertisements
Similar presentations
Project management.
Advertisements

Risk The chance of something happening that will have an impact on objectives. A risk is often specified in terms of an event or circumstance and the consequences.
Note: See the text itself for full citations. Information Technology Project Management, Seventh Edition.
Introduction to Risk Management 26 September 2014 Peter Fowler CPPD.
Project Management Risk Management. Outline 1.Introduction 2.Definition of Risk 3.Tolerance of Risk 4.Definition of Risk Management 5.Certainty, Risk,
Risk Analysis & Management. Phases Initial Risk Assessment Risk Analysis Risk Management and Mitigation.
Risks  All projects have some degree of risk  Risks are issues that can cause problems  Delay in schedule  Increased project costs  Technical risk.
W5HH Principle As applied to Software Projects
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Project.
Projmgmt-1/33 DePaul University Project Management I - Risk Management Instructor: David A. Lash.
Chapter 6 Section 1 Introduction. Probability of an Event The probability of an event is a number that expresses the long run likelihood that an event.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 Project management.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 COMP201 Project Management.
Software project management (intro)
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Chapter 4 Project Management “…a huge topic.” See Part 6, “Management”, Chaps.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
1 SOFTWARE PRODUCTION. 2 DEVELOPMENT Product Creation Means: Methods & Heuristics Measure of Success: Quality f(Fitness of Use) MANAGEMENT Efficient &
Title slide PIPELINE QRA SEMINAR. PIPELINE RISK ASSESSMENT INTRODUCTION TO GENERAL RISK MANAGEMENT 2.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects l.
Project Management Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
贾银山 Software Engineering, Chapter 5 Slide 1 Project management.
©Ian Sommerville 2006Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering.
©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 5 Slide 1 Chapter 5 Project Management Modified by Randy K. Smith.
Project management DeSiaMore 1.
Risk Management & Liability Informa Brownfield Hospital Development Summit June 2009.
Project Risk Management: An Overview Andrew Westdorp Program Manger, IV&V Lockheed Martin (301)
Project Risk Management Supplement. The Importance of Project Risk Management  Project risk management is the art and science of identifying, assigning,
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Concerned with activities involved in ensuring that software is delivered: on.
HIT241 - RISK MANAGEMENT Introduction
November, 2000 Slide 1 Project Services Division RISK MANAGEMENT Project Services Division Presentation By: Adam Malkhassian November, 2000.
Risk Management - the process of identifying and controlling hazards to protect the force.  It’s five steps represent a logical thought process from.
Section Topics Establish a framework for assessing risk
1 TenStep Project Management Process ™ PM00.7 PM00.7 Project Management Preparation for Success * Manage Risk *
Managing Project Resources. Project Resources Human Resources Project stakeholders: – Customers – Project team members – Support staff Systems analyst.
Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Project management Lecture 10. Topics covered Management activities Project planning Project scheduling Risk management.
Chapter 15: Risk Management
©Ian Sommerville 2000 Slide 1 Project management l Organising, planning and scheduling software projects l Objectives To introduce software project management.
Lecture 7 Risk Analysis CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
Risk management (lecture). D efinitions of risk General: standard deviation Finance: volatility of return and costs Risk in project management (Lockyer.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
COOP Seminar – Fall 2008 Slide 1 HOUSTON COMMUNITY COLLEGE SYSTEM SAIGONTECH SAIGON INSTITUTE OF TECHNOLOGY Software Project Management.
Chapter 3 Project Management Chapter 3 Project Management Organising, planning and scheduling software projects.
Project Management IV1021Fö5 Risk Management. Agenda Project Risk Project Risk Management The Risk Management Process Goal: get an understanding of basic.
Software Engineering, 8th edition. Chapter 5 1 Courtesy: ©Ian Sommerville 2006 Oct 13 th, 2008 Lecture # 6 Project management.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
1 Project management. 2 Topics covered Management activities Project planning Project scheduling Risk management.
Dr Izzat M Alsmadi Edited from ©Ian Sommerville & others Software Engineering, Chapter 3 Slide 1 Project management (Chapter 5 from the textbook)
Chap 4. Project Management - Organising, planning and scheduling
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Project management 1/30/2016ICS 413 – Software Engineering1.
1 Project Management C53PM Session 4 Russell Taylor Staff Work-base – 1 st Floor
Erman Taşkın. Information security aspects of business continuity management Objective: To counteract interruptions to business activities and to protect.
Risk Managament in Software Engineering Abdul Serwadda.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Chapter 4: Project management l Organising, planning and scheduling software.
Project management (2) By: Zhou Chunlin School of Tourism, Conference and Exhibitions Henan University of Economics and Law.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
Project management. Software project management ■It is the discipline of planning, organizing and managing resources to bring about the successful completion.
Chapter 3 Project Management Parts of this presentation is extracted from Ian Sommerville’s slides located at
Ashima Wadhwa.  Probably the most time-consuming project management activity.  Continuous activity from initial concept through to system delivery.
1 Project management Organising, planning and scheduling software projects.
Updated Risk Management template
An Overview on Risk Management
Recognization and management of RISK in educational projects
Software Project Management (SPM)
Risk management.
Risk management.
Presentation transcript:

Defence Project Management 2007 Learning to love project risk management Dr Andrew Tyler DG Ships, DE&S

Defence projects – more risky than most Military superiority –Complexity risk –Technology maturity risk Complex procurement strategies (multi-party, multi- national etc.) Complex market context Politics

Defence project risk management Project management & risk management are synonymous –The risk - to what….? –Risk, issues, and uncertainty –Risk perception –Expressing risks –Risk management actions –Quantifying risks –Linking risks and project forecasting

The risk to what……? The risk to what? –Business objectives, safety, financial targets etc. etc. Express risk impact in the right currency –£££s, time delay, lost time accidents etc. etc.

Risk, issues, and uncertainty “….as we know, there are known unknowns; there are things we know we know. We also know there are known unknowns; that is to say we know there are some things we do not know. But there are also unknown unknowns – the ones we don’t know we don’t know.” Donald Rumsfeld

Identifying a risk A risk is an event or situation with a realistic likelihood of occurring and an unfavourable consequence should it occur – the known unknowns If you don’t know what it is, it’s an uncertainty – the unknown unknowns If it has occurred already, it is an issue – known knowns Risks can be specifically identified and quantified in the appropriate currency

Risk perception Dogs risk management in many fields - especially public perception of risk Less so in project risk management but; High impact, low probability risks (usually dramatic and eye-catching) usually over- stated subjectively and understated quantitatively

Expressing risks Specificity is key; “There is a risk we could lose key staff” Cause-effect-consequence “There is a risk that the hot market for software engineers may result in loss of senior software designers leading to delay in completing our system design review on time”

Risk management actions Specificity is key –Assigned to a single responsible individual –Specific action(s) achievable within a realistic period (6-12months) “HR manager to implement golden handcuffs scheme within 3 months” Can sometimes be a good way of testing risk expression

Quantifying risks A very tricky area – but essential Computer models can be very misleading; –Statistical approaches often suppress high impact, low probability risks –Risk envelope often too tight at outset – risky projects with only 5-10% difference between 10% and 90% probabilities of out-turn –Risk inter-dependencies often not well handled –Risks to schedule are almost always risks to cost – easy to count twice –‘Black box’ nature often leads to mistakes –Ability to run models regularly is essential

Managing the project risks The project team is there for one reason only – to manage risks If it weren’t for the risks, the project team would consist of a contracts officer…..and that’s all What matters is how the risks are identified, quantified and managed The movement in the risk profile is the heartbeat of the project – no movement, no life

Linking risk to project forecasting Project Performance Metric e.g. time, cost Time MOST PROBABLE OPTIMISTIC PESSIMISTIC Project milestone deliveries Early stage risk identification Risk mitigation planning Late emerging risk and mitigation Zero risk Project End Initial Risk Envelope

Evidence of active risk management?

Project re- approval – risks reassessed New risk(s) identified Risk mitigation in place Note risk asymmetry Risk ‘funnel’ reducing

Opportunity management An opportunity; –A situation or circumstance with a realistic likelihood of occurring, and which provides a potential benefit Mature risk management embraces risks and opportunities equally

CVF risk and opportunity management Early introduction of Earned Value Management Discipline of work breakdown structure and single point responsibility established (Cost Account Manager) Every CAM owns quantified risk and opportunity against base cost/time Held in central model - rolled up monthly to provide holistic project performance forecast

Defence project risk touchstones Centralised risk systems with hundreds of risks are unmanageable unless highly federated with single-point-of-accountability Specificity in risk expression and actions Quantification of risk is a minefield – beware! Project forecasts should be moving constantly against the changing risk/opportunity profile Risk and opportunity should be treated as equals In a Department of State, political risks are rarely treated honestly