Risk Management CS 414, Software Engineering I Mark Ardis, Rose-Hulman Institute January 28, 2003.

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

Software Quality Assurance Plan
MITIGATING RISK Knowledge Management Initiatives.
Planning at CMM level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements Engineering.
Software Quality Assurance Plan
More CMM Part Two : Details.
CSSE September.2008 Risk Chapter 2, pages “At risk”
Introduction CS 414, Software Engineering I Mark Ardis and Don Bagert Rose-Hulman Institute December 2, 2002.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
School of Computing, Dublin Institute of Technology.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
1 Chapter 6 Risk Management. 2 Project Risks What can go wrong? What is the likelihood? What will the damage be? What can we do about it?
Types of Risks 1.Project risks –Impact schedule and cost –Includes budgetary, schedule, personnel, resource, customer, requirement problems 2.Technical.
Software Engineering Institute Capability Maturity Model (CMM)
Fundamental of Software Project Management
CMM Level 3 KPA’s CS4320 Fall Organizational Process Focus (Goals) Software process development and improvement activities are coordinated across.
Project Management: Madness or Mayhem
Software Project Management
Chapter 25 Risk Management
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
OHT 16.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The objectives of training and certification The training and certification.
Software Engineering Risk Management. Steps in Project Planning lScope—understand the problem and the work that must be done. lEstimation—how much effort?
Software Project Management Lecture # 8. Outline Chapter 25 – Risk Management  What is Risk Management  Risk Management Strategies  Software Risks.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Process Standardization Project
1 Chapter 6 Risk Management. 2 Project Risks What can go wrong? What is the likelihood? What will the damage be? What can we do about it?
Software Project Management Lecture # 8. Outline Earned Value Analysis (Chapter 24) Topics from Chapter 25.
Copyright 2010, The World Bank Group. All Rights Reserved. Statistical Work Plan Development Section B 1.
Chapter 2 Project Management Lecture 1 1Chapter 22 Project management.
Configuration Management (CM)
Software Project Management Lecture # 7. Outline Project Scheduling.
Lecture3 : Change Control Lecturer: Kawther Abas 447CS – Management of Programming Projects.
Software Engineering Risk Management. Understanding Risks Risks involve :  Uncertainty – there are no 100% probable risks  Loss – if the risk becomes.
Risk Analysis & Management
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
What is it? A risk is a potential problem — it might happen, it might not. But, regardless of the outcome, it’s a really good idea to identify it. Assess.
Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004.
Georgia Institute of Technology CS 4320 Fall 2003.
©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.
Project Management Yonsei University 2 nd Semester, 2012 Sanghyun Park.
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.
Risk Analysis 1. Project Risks 2 What can go wrong? What is the likelihood? What will the damage be? What can we do about it? Check : List of potential.
Software Engineering B.Tech IT/II Sem-II Term: Unit-7 PPT SLIDES Text Books:1.Software Engineering, A practitioner’s approach Roger s. Pressman.
Software Engineering Lecture 6: Risk Analysis & Management.
Chap 4. Project Management - Organising, planning and scheduling
CSC 480 Software Engineering Lecture 5 September 3, 2004.
The Implementation of BPR Pertemuan 9 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Software Project Management Lecture # 9. Outline Chapter 25 – Risk Management  What is Risk Management  Risk Management Strategies  Software Risks.
Project Management Why do projects fail? Technical Reasons
Illuminating Britelite’s Internal Services for Success Strategy for Process Improvement.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Managing Multiple Projects Steve Westerman California Department of Motor Vehicles Steve Young Mathtech, Inc.
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
T Project Review X-tremeIT I1 Iteration
Configuration Management
Software Configuration Management (SCM)
Configuration Management
Software Engineering B.Tech Ii csE Sem-II
Risk Analysis.
Recognization and management of RISK in educational projects
Assessing Risk Impact Factors affecting the consequences Nature Scope
Chapter 28 Risk Analysis Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides copyright © 1996, 2001,
Chapter 6 Risk Management
Project Management Group
Project Name Here Kick-off Date
Presentation transcript:

Risk Management CS 414, Software Engineering I Mark Ardis, Rose-Hulman Institute January 28, 2003

2 Outline u Identification u Estimation u Mitigation u Exercise

3 First Cartoon of the Day

4 Risk Item Checklists u Product Size u Business Impact u Customer-related u Process u Technology u Development Environment u Staff Size and Experience

5 Product Size u Estimated size of the product in LOC or function points? u Degree of confidence in estimated size estimate? u Number of users of the product? u Number of projected changes to the requirements for the product? Before delivery? after delivery?

6 Business Impact u Affect of this product on company revenue? u Number of customers who will use this product? u Number of other products/systems with which this product must be interoperable?

7 Customer-related u Does the customer have a solid idea of what is required? Has the customer spent the time to write it down? u Is the customer willing to participate in reviews? u Is the customer technically sophisticated in the product area?

8 Process u Are staff members "signed-up" to the software process as it is documented and willing to use it? u Is the software process used for other projects? u Are formal technical reviews conducted regularly?

9 Technology u Are specific methods used for software analysis? u Are configuration management software tools used to control and track change activity throughout the software process? u Are metrics collected for all software projects?

10 Development Environment u Are compilers or code generators available and appropriate for the product to be built? u Are all software tools integrated with one another? u Have members of the project team received training in each of the tools?

11 Staff Size and Experience u Do the people have the right combination of skills? u Are enough people available? u Are staff committed for entire duration of the project? u Will some project staff be working only part time on this project? u Have staff received necessary training?

12 Outline u Identification u Estimation u Mitigation u Exercise

13 Second Cartoon of the Day

14 Risk Estimation 1. List all possible risks 2. Assign a probability to each 3. Assign an impact to each 4. Sort by probability and impact

15 Sorted Risks Low Impact Moderate Impact High Impact Low Probability Moderate Probability High Probability Criticality 1 Criticality 2 Criticality 3 Criticality 4 Criticality 5 Criticality 6 Yellow Green Red

16 Outline u Identification u Estimation u Mitigation u Exercise

17 Risk Mitigation u Develop a strategy for each risk – May require some creativity – May use successful strategies from past u Apply each strategy u Monitor for changes

18 Outline u Identification u Estimation u Mitigation u Exercise

19 Problem u You and 7 others are going to fly 1500 miles in a pedal-powered airplane. u The plane can carry 3000 pounds of freight (including passengers) at 30 mph, when powered by 4 pedallers. u Each team member can pedal for 4 hours continuously. u If you lose power the plane crashes.

20 Exercise 1. Identify the risks 2. For each risk, estimate its probability and impact 3. Prioritize risks 4. Identify mitigation strategies for the most important half of the risks 5. Share your results with rest of class