This report outlines risk management in general and considers risks within the early stages of a development lifecycle in relation to IT projects. Also the paper will analyze the hiring and termination policy. The paper will create a project plan for implementing an Intrusion Detection System. Finally the paper will perform the Web search for terms “disaster recovery” and “business continuity”.
Risk assessment tools
Risk Assessment and Management
The risk assessment is the articulation of risks in terms of their likelihood and seriousness. Risks should be focused on from the start of a project, at conceptual stages and then watched closely as projects proceed. Insight in to early project factors likely to threaten project success will help project managers and other stakeholders to better predict the likelihood of their projects success (Proccaccino, 2002). Many organisations around the world quantify risks of new IT infrastructures based on risk management techniques rather that just proceeding on a project. This is due to the disasters caused by IT failures in the past. A classic example would be the London Ambulance services effort to automate ambulances at critical periods around London, which collapsed when brought online, no risk assessment or contingency was developed to manage and resolve risks. Poor requirements are involved in most project failures (Verner, 2002). The requirements need to be addressed using risk assessment and management techniques. Risk management is the process of dealing with the identified and assessed risks (Wharton 1992). Risk management techniques and methodologies can be implemented within organisations to combat risks at the early stages of the lifecycle, for example at the initiation and selection stages, risk analysis identifies risks and then at the evaluation stages of IT project, risks management can be criticised and improved for the future.
Proactive and Reactive tools to Risk Management
Risk assessment and risk evaluation at the initiation stages can take form in two different ways. Firstly risks can be identified by the management in a reactive manner, this is when risks are only combated when they have turned in to problems and the stakeholders take this in to account at this stage. Thus when risks become problems then they are combated against, a clear disadvantage it that at the initiation stages of a project it would not have countermeasures in place to combat risks and therefore no contingency. Conversely to this, risks can be identified and assessed in a proactive manner where potential risks are evaluated and contingency planning is carried out before the risk ever becomes a problem (Pressman, 2000). Proactive risk management is the aim within IT projects but it is sometimes difficult to estimate occurrences of risk let alone develop countermeasures.
Qualitative and Quantitative Risk tools
As established earlier a proactive approach to risk seems more appropriate to reacting to risk and therefore quality and quantity need to be assessed proactively. Quantitative decisions are based on an exhaustive collection of data, which all too often costs huge amounts of money, and the data can become redundant ...