Risk Management CS 414 Software Engineering I Mark

  • Slides: 20
Download presentation
Risk Management CS 414, Software Engineering I Mark Ardis, Rose-Hulman Institute January 28, 2003

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

Outline u Identification u Estimation u Mitigation u Exercise 2

Outline u Identification u Estimation u Mitigation u Exercise 2

First Cartoon of the Day 3

First Cartoon of the Day 3

Risk Item Checklists u Product Size u Business Impact u Customer-related u Process u

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

Product Size u Estimated size of the product in LOC or function points? u

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? 5

Business Impact u Affect of this product on company revenue? u Number of customers

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? 6

Customer-related u Does the customer have a solid idea of what is required? Has

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? 7

Process u Are staff members "signed-up" to the software process as it is documented

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? 8

Technology u Are specific methods used for software analysis? u Are configuration management software

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? 9

Development Environment u Are compilers or code generators available and appropriate for the product

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? 10

Staff Size and Experience u Do the people have the right combination of skills?

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? 11

Outline u Identification u Estimation u Mitigation u Exercise 12

Outline u Identification u Estimation u Mitigation u Exercise 12

Second Cartoon of the Day 13

Second Cartoon of the Day 13

Risk Estimation 1. 2. 3. 4. List all possible risks Assign a probability to

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

Sorted Risks High Probability Yellow Criticality 4 Moderate Probability Green Criticality 5 Low Probability

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

Outline u Identification u Estimation u Mitigation u Exercise 16

Outline u Identification u Estimation u Mitigation u Exercise 16

Risk Mitigation u Develop – – a strategy for each risk May require some

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 17

Outline u Identification u Estimation u Mitigation u Exercise 18

Outline u Identification u Estimation u Mitigation u Exercise 18

Problem u You and 7 others are going to fly 1500 miles in a

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. 19

Exercise 1. 2. 3. 4. 5. Identify the risks For each risk, estimate its

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