软件项新教材目管理(新)资料.ppt

Risk avoidance Some activities may be so prone to accident that it is best to avoid them altogether. If you are worried about crocodiles then don’t go into the water. For example, given all the problems with developing software solutions from scratch, managers might decide to retain existing clerical methods, or to buy an off –the –shelf solution. Risk reduction Here we decided to go ahead with a course of action despite the risks, but take precautions that reduce the probability of the risk. This chapter started with a scenario where two of the staff scheduled to work on Amanda’s development project at IOE departed for other jobs. If this has been identified as a risk, steps might have been taken to reduce possible departures of staff. For instance, the developers might have been promised generous bonuses to be paid on successful completion of the project. Recall that Brigette had a problem at Brightmouth College: after the purchase of the payroll package, a requirement for the payroll database to be accessed by another application was identified. Unfortunately, the application that had been bought did not allow such access. Brigette might have specified that the selected package must use a widely accepted data management system like Oracle that allows easier integration. Risk mitigation can sometimes be distinguished from risk reduction. Risk reduction attempts to reduce the likelihood of the risk occurring. Risk mitigation is action. Risk transfer In this case the risk is transferred to another person or organization. With software projects, an example of this would be where a software development task is outsourced(外包) to an outside agency for a fixed fee. You might expect the supplier to quote a higher figure to cover the risk that the project takes longer than the ‘average expected time. On the other hand, a well-established external organization might have productivity advantages as its developers are experienced in the type of development to be carried