Risk planning Risks can be dealt with by: Risk acceptance – the cost of avoiding the risk may be greater than the actual cost of the damage that might.

Slides:



Advertisements
Similar presentations
Chapter 7 Managing Risk.
Advertisements

Managing Risk CHAPTER SEVEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
AACEI Contingency Forum Contingency Management
CP Chapter 4 Schedule Planning.
Project management l Organising, planning and scheduling software projects l Objectives To introduce software project management and to describe its distinctive.
Defining activities – Activity list containing activity name, identifier, attributes, and brief description Sequencing activities – determining the dependencies.
OPSM 639, C. Akkan1 Defining Risk Risk is –the undesirable events, their chances of occurring and their consequences. Some risk can be identified before.
Project Management.
Spring 2008, King Saud University PERT Dr. Khalid Al-Gahtani 1 Activity Duration 1.“Guess” the activity duration, especially smaller activities. 2.Use.
Chapter 7: Managing Risk
Computer Engineering 203 R Smith Risk Management 7/ Risk Management The future can never be predicted with 100% accuracy. Failure to plan for risks.
Software project management (intro)
COSYSMO Risk/Confidence Estimation Prototype John Gaffney March 14, 2005.
Chapter 8 Risk Analysis Management of Computer System Performance.
Risk Management. What is risk? You have some expected outcome –Of some event in the future Risk is the deviation of the actual future outcome from the.
Prepared by: Michael Palazzo
OPER 576 Project Management Reducing Project Duration or Project Crashing Greg Magnan, Ph.D. May 20, 2004.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Concerned with activities involved in ensuring that software is delivered: on.
Risk Management A Key Project Management Knowledge Area.
Managing Risk. Objectives  To Describe Risk Management concepts and techniques  To calculate and analyze a project using Probability of completion 
Risk management process
Software Engineering Process - II 3.1 Unit 3: Risk Management Software Engineering Process - II.
CS3100 Software Project Management
Managing Risks in Projects. Risk Concepts The Likelihood that some Problematical Event will Occur The Likelihood that some Problematical Event will Occur.
Chapter 7: Risk Management Project Management Afnan Albahli.
MARCH 1 Risk Management Why carry out Risk Assessment? l Is the project too risky? l Threat intensity? l Improve decision making l Clarification of terms.
1 Chapter 5 Project management. 2 Project management : Is Organizing, planning and scheduling software projects.
Managing Project Resources. Project Resources Human Resources Project stakeholders: – Customers – Project team members – Support staff Systems analyst.
6-1 ELC 347 project management Day 13. Agenda Questions Assignment 5 posted –Due Oct 12:35 PM Integrative Project part 2 feedback –You needed more.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
© The McGraw-Hill Companies, Software Project Management 4th Edition Risk management Chapter 7.
Risk Management A Key Project Management Knowledge Area An Essential Part of the Project Plan © Edward B. Farkas, CHS, CPM, MIEEE, PMP.
Risk management (lecture). D efinitions of risk General: standard deviation Finance: volatility of return and costs Risk in project management (Lockyer.
Ch 10 - Risk Management Learning Objectives You should be able to: List and describe risk management processes, inputs, outputs, and tools List and describe.
1 Risk Management 2 n IEEE defines risk as: “the likelihood of an event, hazard, threat or situation occurring and its undesirable consequences” [Std.
Project Management All projects need to be “managed” –Cost (people-effort, tools, education, etc.) –schedule –deliverables and “associated” characteristics.
Risk and Procurement These slides have been added to the standard MRU PM Cert materials and are made available to students who have attended my class.
Chapter 6: Project Time Management Information Technology Project Management, Fourth Edition Using Critical Chain Scheduling, PERT, and MS Project 2003.
Chapter 7 PERT Project Management for Business, Engineering, and Technology.
Q N U Schedule Risk Management By Ursula Kuehn, PMP, EVP UQN and Associates.
1 3. M ODELING U NCERTAINTY IN C ONSTRUCTION Objective: To develop an understanding of the impact of uncertainty on the performance of a project, and to.
Managing Risk CHAPTER SEVEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Managing Risk CHAPTER SEVEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
PERT/Activity Diagrams, Completion Probability and the Z Score
Software Project Management Lecture 5 Software Project Risk 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.
CPM – Critical Path Method Can normal task times be reduced? Is there an increase in direct costs? Additional manpower Additional machines Overtime, etc…
University of Sunderland CIFM02 Unit 5 COMM02 Project Hazard Management and Contingency Planning Unit 5.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Chapter 7 : Risk Management – part 2
5 th LectureCEN 4021: Software Engineering II Task Sequence and Effort representation  All tasks share at least two basic characteristics –Require effort.
Chapter 8 Risk Management Plans 8 Risk Management Plans C H A P T E R.
R i s k If you don’t attack risks, they will attack you.
PROJECT MANAGEMENT week 8
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.
PERT/Activity Diagrams, Completion Probability and the Z Score
Software Project Management 4th Edition
RISK MANAGEMENT.
Software Project Management
Activity Planning.
Prepared By: Prof.Rucha Patel
Software Project Management (SPM)
Software Project Management
Management. Management What is a risk? A risk is simply a probability that some adverse circumstance will actually occur.
Risk management.
Software Project Management 4th Edition
Risk management.
PERT/Activity Diagrams, Completion Probability and the Z Score
Managing Risk Chapter 7.
Presentation transcript:

Risk planning Risks can be dealt with by: Risk acceptance – the cost of avoiding the risk may be greater than the actual cost of the damage that might be inflicted Risk avoidance – avoid the environment in which the risk occurs e.g. buying an OTS application would avoid a lot of the risks associated with software development e.g. poor estimates of effort. Risk reduction – the risk is accepted but actions are taken to reduce its likelihood e.g. prototypes ought to reduce the risk of incorrect requirements

Risk transfer – the risk is transferred to another person or organization. The risk of incorrect development estimates can be transferred by negotiating a fixed price contract with an outside software supplier. Risk mitigation – tries to reduce the impact if the risk does occur e.g. taking backups to allow rapid recovery in the case of data corruption

Reducing the risk Hazard Prevention – eg: key staff unavailable for meeting – early scheduling Likelihood Reduction – those cannot be prevented – reduce the likelihood – eg late changes to requirement specification – prototype Risk avoidance – eg : overrunning the schedule – increasing duration estimates Risk transfer –impact transferred away from the project - eg – contracting Contingency planning – eg : unplanned absence of programming staff – agency programmers.

Evaluating risk to schedule Effect of uncertainties on project schedule Using PERT Three estimates are produced for each activity Most likely time (m) the time we would expect the task to take normally Optimistic time (a) the shortest time in which we could expect to complete the activity, barring outright miracles Pessimistic (b) worst possible time (only 1% chance of being worse, say) ‘expected time’ t e = (a + 4m +b) / 6 ‘activity standard deviation’ S = (b-a)/6

PERT technique uses three – step method for calculating the probability of meeting or missing target – Calculate the standard deviation of each project event – Calculate the z value for each project event that has the target date – Convert z values to a probabilities

Calculating the z value z = (T – t e )/s T – Target date Convert z value to probability A z value may be converted to the probability of not meeting the target date by the graph

Graph of z values