Web server info - 128 Part II: Planning Your Software Project Transferring
128 Part II: Planning Your Software Project Transferring risks Have you ever just wanted to get someone else to do a portion of a project because the technology involved was too complex, you were unfamiliar with a new programming language, or you feared that the impact of the project on your organization, if the project failed, would be too great? Probably so. If you ever went forward with the procurement process and hired a consultant to do the project for you, or even farmed out a risky portion of a project, you ve completed transference. Transference means that the risk doesn t go away. It s just someone else s responsibility now. You ve used transference if you ve ever done any of the following: Purchased insurance, such as errors and omissions insurance Hired experts to complete a portion of the project work Demanded warranties from vendors Brought in consultants to test units and builds of your software Be aware that the risk has not disappeared; you have just transferred it. In fact, if the vendor doesn t deliver on time, you still absorb the impact. Transferring risks introduces a whole new set of risks that you and your team must identify, analyze, and respond to. Mitigating risks Risk mitigation is about reducing the impact and/or the probability of risk. Remember qualitative and quantitative risk analyses? (If not, read some of the earlier sections in this chapter.) When you implement risk mitigation strategies, you typically examine the risks with medium to high scores for risk mitigation opportunities. In other words, you attempt to answer questions like, How can the impact, the probability, or both be reduced to a level that we can live with? Ideally, you d like to reduce both the impact and the likelihood of a risk occurring, but often when you re mitigating risk you choose to mitigate either one or the other usually you suck it up and accept the lesser of two evils. You ve used mitigation if you ve ever done the following: Added extra testing, verification, or customer approval activities to ensure that the software conforms to requirements Reduced the number of processes, activities, or interactions within a smaller project to streamline and focus project management activities on accomplishing specific project tasks
Note: If you are looking for cheap webhost to host and run your apache application check Vision apache web hosting services