Space web hosting - 118 Part II: Planning Your Software Project The
118 Part II: Planning Your Software Project The impact of each risk is quantified by a negative dollar amount or by an assessment of time lost, though some organizations turn time into dollars. This negative dollar amount represents the cost the project will incur if the risk event occurs. Notice that the rebate from the manufacturer risk will actually save the project $1,000 if it comes to fruition. The sum of the risk event values, both positive and negative, is the amount of contingency funds that should be reserved for this project. Don t get too excited that the amount of the contingency reserve is less than the sum of all the risks. The probability for all of the risks occurring is not 100 percent, so you won t get 100 percent of the dollar amount associated with each risk. You re banking that some of the risk events will occur and some of the events won t. Using Software Models for Risk Management Within software project management, there are models that help the project manager alleviate the biggest risk of them all failure. Models are adapted from grandfather programs, serious thought and planning, or they evolve based on past experience. Whatever approach you or your organization takes, the model needs to be documented, and the rules need to be defined and then followed. Avoiding the code-and-fix model The code-and-fix model of risk management understand the operation, so they hack away is hardly a model at all, but we remain amazed until the cash and time dribbles away or light- at how often we discover its use when we ning strikes and they declare, It s alive! consult with various companies. The code-and- The code part comes first, and it s followed by fix model is reactionary and it s rubbish. rounds (and rounds) of fixing. This model, if you Basically, you start out with a dreamy set of really want to call it that, is weak, weak, weak. requirements and willing programmers. The It might be ideal for an afternoon of prototyping project manager and the project team meet, yak or playing what-ifs, but it s a risk-enriched about the software, and then coding begins. approach (that is an approach that is chock-full Everyone holds their breath like they re in of risks); in fact, it s the highest-risk model you the waiting room of the hospital. The program-can use in software development. Avoid it like, mers are the surgeons, but they really don t well, just avoid it.
Note: In case you are looking for affordable webhost to host and run your servlet application check Vision make web site services