Chapter 5: Planning for Software Project Risks 129 (Best web hosting)
Chapter 5: Planning for Software Project Risks 129 Developed and tested prototypes, used user acceptability testing processes, or launched pilot groups within your organization before releasing the software Accepting the risks When you accept certain risks, either the risks are so low that the project can live with them, or the risks are inevitable but the project must move forward anyway. Sometimes you just know that you can t prevent an identified risk, you just suck it up, work towards a solution, and deal with it. Here s an example of risk acceptance. Say you re working with a non-collocated team and you ll be doing lots of traveling between sites to manage and lead the project team. A risk that you have to accept, like it or not, is weather. Weather delays could affect the project and you have very little response to weather delays other than communicating electronically. Usually, risk acceptance is for the smaller, puny risks that have a very low probability, a very low impact, or both. However, any risk you do not identify, you automatically accept! Examining Risk Responses and Impacts Have you ever made one small change to your software development plan and watched, aghast, as the change mushroomed into a huge issue that delayed your project for weeks? The same thing can happen with your risk response plan. Before a risk response is implemented, the project manager and the project team need to examine the full effect of the response. The project team and the project manager should determine when the risk response should be implemented. Two terms here to recognize are Risk threshold: The line of demarcation that signals that a risk is about to come into play and that some response should happen. The risk threshold can be a date for completion, a percentage of the work that is not complete, a failed test, or any other event that signals a pending risk. Risk trigger: A trigger is an event within the project that triggers a pre- planned response to the identified risk. Thresholds and triggers often work together. For example, you may decide that if the project is not 50 percent complete by March 1 then you risk missing the final deadline. To reduce this risk, you plan to hire consultants to help finish the project if that March 1 deadline isn t met. The threshold is the requirement for March 1, and the trigger is whether or not the project is 50 percent complete.
Note: If you are looking for best quality webspace to host and run your tomcat application check Vision virtual web hosting services