Managing Project Risks and Opportunities

Slides:



Advertisements
Similar presentations
PROJECT RISK MANAGEMENT
Advertisements

Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Computer Engineering 203 R Smith Project Tracking 12/ Project Tracking Why do we want to track a project? What is the projects MOV? – Why is tracking.
Project Management.
1 The Role of the Revised IEEE Standard Dictionary of Measures of the Software Aspects of Dependability in Software Acquisition Dr. Norman F. Schneidewind.
Issue Tracking John D. McGregor Module 10 Session 1 Issue Tracking and Risk.
W5HH Principle As applied to Software Projects
What is a project? Project Management Institute definition
1 Introduction to System Engineering G. Nacouzi ME 155B.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Types of Risks 1.Project risks –Impact schedule and cost –Includes budgetary, schedule, personnel, resource, customer, requirement problems 2.Technical.
CIS 375 Bruce R. Maxim UM-Dearborn
Project Risk Management Risk Mitigation. Risk Management  The prime objective of risk management is to minimize the impact and probability of the occurrence.
Project Execution.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
DEPARTMENT OF REGIONAL DEVELOPMENT, PRIMARY INDUSTRY, FISHERIES AND RESOURCES Mining Management Act Workshop and Information Session Mining Operations.
Feasibility Study.
Managing Risks in Projects. Risk Concepts The Likelihood that some Problematical Event will Occur The Likelihood that some Problematical Event will Occur.
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
1 Chapter 5 Project management. 2 Project management : Is Organizing, planning and scheduling software projects.
Object-Oriented Software Engineering
Chapter 22 – Risk Management 1Chapter 22 Project management.
©Ian Sommerville 2000 Slide 1 Project management l Organising, planning and scheduling software projects l Objectives To introduce software project management.
1 The Concept of Risk A risk is defined as a variable that can take a value that endangers or eliminates success for a project. In plain terms, a risk.
Chapter 3 Project Management Chapter 3 Project Management Organising, planning and scheduling software projects.
Ch 10 - Risk Management Learning Objectives You should be able to: List and describe risk management processes, inputs, outputs, and tools List and describe.
Software Project Management Lecture 5 Software Project Risk Management.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 3 Managing the Information Systems Project 3.1.
Chap 4. Project Management - Organising, planning and scheduling
RISK MANAGEMENT YULVI. Introduction Time Quality Cost Project Constraints Success Introduction.
Information Technology Project Management Managing IT Project Risk.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
ICS Area Managers Training 2010 ITIL V3 Overview April 1, 2010.
Case Study of Agile Development Ronald J. Leach Copyright Ronald J. Leach, 1997, 2009, 2014,
1 Week 3 Software Engineering Spring Term 2016 Marymount University School of Business Administration Professor Suydam.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
WEEK 7 Project Management Magister Desain Universitas Komputer Indonesia.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
COMP201 Project Management.
ISQB Software Testing Section Meeting 10 Dec 2012.
James W. Bilbro JB Consulting International Huntsville, AL
Software Configuration Management
Application Outsourcing: Achieving Success & Avoiding Risk
School of Business Administration
11.1 Plan Risk Management The process of defining how to conduct risk management activities for a project Detailed risk planning enhances the overall probability.
ERP = Enterprise Resource Planning
Project management.
Software Processes (a)
Real Exam Questions Answers
Case Study: The Accounting Software Installation Project
Risk management Chapter 7 Copyright ©2016 Pearson Education, Inc.
Constructive Cost Model
BUS 519 Education for Service-- snaptutorial.com.
BUS 519 Teaching Effectively-- snaptutorial.com
Software Project Management (SPM)
FOUNDATIONAL CONCEPTS
Risk Analysis & Success Driven Project Management
Figure 3: Risk Analysis Model
Inspection and Review The main objective of an Inspection or a Review is to detect defects. (Not for Giving Alternative Solutions) This activity and procedure.
Chapter 6 Risk Management
Planning a Project Chapter 2.
Cycle Time Efficiency Model
Software Testing Lifecycle Practice
ISSUE MANAGEMENT PROCESS MONTH DAY, YEAR
Chapter 3 Managing the Information Systems Project
Chapter 4: Software Process Models
Information system analysis and design
Presentation transcript:

Managing Project Risks and Opportunities MGMT 412 Week 3 Chat

MGMT 440 Week 2 Chat

Scenario The design manager and the engineering manager were discussing with you the software tool they normally use for their design and engineering work. It is critical to their process, but there are some defects in the software that result in errors in the designs. MGMT 412 Week 3 Chat

Scenario The team knows how to find the errors and correct them, but it takes additional time during the design and engineering timeline. The managers just received an e-mail from the software vendor stating that a new version of the tool will be available right as the design tasks are expected to begin. MGMT 412 Week 3 Chat

Scenario Historically, the vendor is known to deliver the software about four weeks later than announced. The upgrade corrects the defects that the team knows about, as well as provides some new functionality that will make some of the engineering tasks faster. MGMT 412 Week 3 Chat

Scenario The vendor is strongly encouraging training for the design and engineering teams to use this new version. As the project manager, you must decide whether or not the team will use this new version of the software. The vendor is offering a 50% discount on the training if people are signed up within the next ten days. MGMT 412 Week 3 Chat

Scenario Answer the following questions: What risks does this use of technology introduce to the project? What is the impact of each risk? What is the probability of each risk? Based on your understanding of the risks, will you tell the managers whether or not they should sign up their people for training? MGMT 412 Week 3 Chat

What risks does this use of technology introduce to the project? MGMT 412 Week 3 Chat

Software Risks A list of potential software risks include: Database complexity Development required Management ability Software complexity Software maturity System size Telecommunication aspects MGMT 412 Week 3 Chat

Suppliers & Sub-contractors Risks Ability to deliver, skills, and quality of the software Accreditation Alternative suppliers and/or sub-contractors Availability Claims and variations Commercial terms Quality of goods and services provided Reliability of supplier Safety attitude Special considerations MGMT 412 Week 3 Chat

Suppliers & Sub-contractors Risks (cont.) Control and supervision Cost of goods and services provided Delivery of goods and services provided Failure of a critical supplier and/or sub-contractor Flow-on conditions from prime contract Lead times for orders Limited number of suppliers or producers New or existing sub-contract Overseas versus local sub-contractors MGMT 412 Week 3 Chat

Suppliers & Sub-contractors Risks (cont.) Stability of joint ventures and/or partnerships Timeliness Transferability of warrantees and/or guarantees Warranty of goods and services provided MGMT 412 Week 3 Chat

Technology Risks A list of technology risks include: Availability of key components Failure rates Lack of technical knowledge Maintenance Need for further development New or non-standard performance Quality requirements MGMT 412 Week 3 Chat

Technology Risks (cont.) Obsolescence Reliability, availability, maintainability Spare parts and support Specification does not reflect client needs Specification incomplete or misleading Technical standards or regulations change Technical standards or regulations unclear Technological change Technology not available MGMT 412 Week 3 Chat

What is the impact of each risk? MGMT 412 Week 3 Chat

Cost, Schedule, and Performance Factors Cost, schedule, and performance are what is impacted by risk. The impact probabilities include: 0.1 = Insignificant 0.3 = Low 0.5 = Medium 0.7 = Very High 0.9 = Catastrophic MGMT 412 Week 3 Chat

0.1 = Insignificant Cost Factor Schedule Factor Performance Factor Budget estimates not exceeded, some transfer of money Negligible impact, slight schedule change compensated by available schedule slack Minimal or unimportant performance impacts MGMT 412 Week 3 Chat

0.3 = Low Cost Factor Schedule Factor Performance Factor Project costs exceed budget by 1% to 5% Minor slip in project schedule, less than 1 month Small reduction in performance MGMT 413 Week 3 Chat

0.5 = Moderate Cost Factor Schedule Factor Performance Factor Project cost estimates increased by 5% to 10% Small slip in project schedule from 1 to 3 months Some reduction in performance MGMT 412 Week 3 Chat

0.7 = Very High Cost Factor Schedule Factor Performance Factor Project cost estimates increased by 10% to 20% Project schedule slip from 3 to 6 months Significant reduction in performance MGMT 412 Week 3Chat

0.9 = Catastrophic Cost Factor Schedule Factor Performance Factor Project costs increased by more than 20% Large project schedule slip, key milestones not achieved Key performance criteria cannot be achieved MGMT 412 Week 3 Chat

Cost, Schedule, and Performance Factors For each risk you will need to determine the following: Whether it is a cost, schedule, or performance factor Whether the impact is insignificant, low, moderate, very high, or catastrophic Read the number that ranges from 0 to 1 from the appropriate table, and then use that number in the succeeding calculations MGMT 412 Week 3 Chat

What is the probability of each risk? MGMT 412 Week 3 Chat

Probability Factors They include: Maturity factors Complexity factors Integration, interfacing, and dependency factors Commercial risk and management process factors MGMT 412 Week 3 Chat

Probability Factors Here are the actual probabilities that you will employ: 0.1 = Rare 0.3 = Unlikely 0.5 = Possible 0.7 = Likely 0.8 = Highly likely 0.9 = Almost certain MGMT 412 Week 3 Chat

Impact & Probability Factors First, you will need to figure out which of the four (4) impact probabilities listed in the previous slides applies. Second, you will need to decide which one of the other six (6) probabilities to assign. Once you have made these two decisions, you have just about answered the question. In the last part of the question, will need to justify your selections. MGMT 412 Week 3 Chat

Based on your understanding of the risks, how will you tell the managers whether or not they should sign up their people for training. MGMT 412 Week 3 Chat

Risk Priority Matrix MGMT 440 Week 2 Chat

Recommended Formula there are two formulas that can be used to calculate the risk factor. The recommended equation is: RF = P + C – (P*C) where P = the selected probability and C = the selected consequence or impact value. MGMT 412 Week 3 Chat

Recommendation All you need to do is substitute the probability and impact factors selected into the equation on the previous slide, perform the calculation, and calculate the result. This will tell you whether or not the team members should or should not sign up for the training. MGMT 412 Week 3 Chat

Example It is obvious that the impact is an interfacing factor. Suppose that you believe that it is unlikely that there will be only minor interfacing problems. Then, the probability value is 0.3, which is read off from the first column of the Table on slide 24 . MGMT 412 Week 3 Chat

Example Next, you will need to decide the impact factor. Since going to training may impact the budget, create a minor slip in the schedule with possibly a small reduction in performance, the impact factor is 0.5. The last step is to substitute these two values into the equation. MGMT 412 Week 3 Chat

Example Here is the calculation: RF = P + C – (P * C) = 0.3 + 0.5 – (0.3 * 0.5) = 0.8 – 0.15 = 0.65 MGMT 412 Week 3 Chat

Example With a 0.65 probability of the training affecting the project schedule, you may come to the conclusion that the training is not worthwhile. This is not an unreasonable conclusion, and so you see how to address this discussion board question. MGMT 412 Week 3 Chat

Caveat Please note that your selection of probabilities may be different from my selection. I encourage you to review the example carefully, specify your own values, and then reach your own conclusions. Then you will have answered the question, and understand how to deal with this elusive issue called risk. MGMT 412 Week 3 Chat