Dynamically Managing Residual Risk

Working to understand the risks a project may endure along with the cost associated is critical in every project management plan. Understanding potential risks based on the project type, resources needed, timeline and budget still leaves gaps that creates uncertainty for actually predicating the outcome of the project. There is not a true way to predict when and where a project risk will occur but designing a plan to properly address and manage those risks will increase confidence while eliminating the element of surprise.

risks and determine the likelihood and consequence of that risk occurring during the project. The

IT projects can have a lot of different components to them which creates the potential for more risks. These risks need to be identified, analyzed, and addressed as the project progresses (Schwalbe Ph.D., 2014). There are different types of risk that can affect the implementation of a system that will allow people to manage their own human resource information. A positive risks can produce a project under budget or ahead of schedule, while a negative risks can have adverse effects on a project such as going way over budget. There are also some risks that do not have a positive or negative impact on a project. Identifying risks and addressing them is mostly handled by the program manager.

Identify a minimum of 10 project risks and when each will occur in the project life cycle, and then determine their impact and probability of occurrence.

When the manager of project carried out its work plan should take into consideration the possible risks that may occur within the project. The risk is the possibility that occurs a problem within a project and that may cause some change within the same (Heldman, 2011). It should be noted that not all risks are bad since they can be potential opportunities to make some changes that will improve the overall status of the project. In the same way a risk not taken into account in time can create one problem in the project and can completely change the final performance of the project. The project manager can take several elements to identify the risks. Some elements and documents that can be used to identify risks are: search internal risks of the project, such as resources

However, when IT projects fall behind schedule, these efficiencies can quickly evaporate and lead to cost overruns, glitches and bugs. (3) Due to their inherently complex nature, IT projects are susceptible to many types of failures; mainly caused by a lack or risk management and flexibility. Many of the risks present in IT projects are unrealistic goals; inaccurate estimates of needed resources; badly defined system requirements; poor reporting of the project’s status; poor communication between developers and users; adoption of immature technology; inability to cope with project complexity; sloppy developed practices; mismanagement of the project; stakeholder politics; and commercial pressures. (4) With so many potential risks, it is not surprising that IT projects that are completed on time, and on budget, are more the exception rather than the rule. Additionally, before IT projects begin, clear objectives and the allocation of time and resources need to be defined; all of which are usually lacking for one reason or another. The result is a high failure rate associated with IT projects overall, which puts a spot light on the need for organizations to improve their risk management abilities and design processes that will allow them the flexibility to reallocate resources when unexpected problems when they

Risks management is an important step during the process of a project. Failing to manage a risk may result in unforeseen event happening and a project’s failure. For example, with limited budget, an unforeseen event or an accident occurs in the middle of a project and this matter has not been considered and needs a big sum of expense, then the project may be stopped because of this unexpected event. We should know it is necessary to understand how to identify risks and assumptions based on the information. After identifying risks, it is important for project managers to set contingency plans to prevent and deal with these risks when they occur. Of course, several problems may happen during considering

Hillson, D & Simon, P. (2007). _Practical Project Risk Management: The ATOM Methodology_, Vienna, VA: Management Concepts, Inc.

Identifying risks is an essential component of planning a large project. A thorough risk analysis is necessary to identify potential issues to the endeavor and assess the probability of therisk occurring, along with the impact on the project if the risk occurs (PMI, 2013). A thorough assessment of the impact that the project will have on the organization should be completed to evaluate the risk of the project, in addition to the impact the project will have on the organization. The risk assessment tool used in Appendix C illustrates the impact this expansion project will have to stakeholders and the organization.

Background- In its most basic sense, risk management identifies, allows assessment, and prioritizes risks that are associated and central to an individual project or organization. Risk management allows the organization to be proactive in preventing or mitigating risks, for improving certain processes within the organization, and with the hope of preventing fiscal exposure. However, in almost every organization there are risks individuals are unique and do not always perform at a high level of safety; mechanical or design failures exist, construction projects have supply or labor issues, there are uncertainties in computer or data modification, of course natural disasters, and even deliberate attacks from competitors, etc. Because this is such a common occurrence, national and even international standards have been developed in conjunction with the insurance and regulatory institutions to at least provide basic guidelines to minimize risks risk (International Organization for Standardization, 2009).

231). It is important to analyze project risk to improve project performance. Therefore as part of this case research and recommendations, an exploration of PMI’s six-stage risk process as outlined in the PMBOK Guide (2008) will be conducted as it relates to risk management alternatives involved with the DIA development with a specific focus on its implementation of an automated area-wide baggage handling system. To evaluate the success of proposed solutions, each stage of the process is presented as an alternative analysis to establish a basic framework of how risk management is approached for this project and the suggested tools utilized to accomplish its overall structure as: (1) risk management planning; (2) risk identification; (3) risk qualification; (4) risk quantification; (5) risk response planning; and (6) risk monitoring and control. Finally detailed recommendations are specified and conclusions drawn that should be implemented with an evaluation process to measure the success of the case review based on the risk analysis presented.

Cisco rapidly grew from a start-up to $500M global corporation by January, 1993 when the case begins with Pete Solvick, CIO of the company faced with the daunting task of upgrading its transaction systems and data warehouse. Cisco had exponential growth through the 1990s, averaging at one point an 80% compound annual growth rate while also accelerating new product development and introductions throughout its direct and indirect sales channels. Systems outages were becoming more common as were product shortcomings due to the IT systems supporting key processes becoming faulty and only partially operating the majority of the time. Clearly Cisco had outgrown its current transaction processes and data warehousing infrastructure.

In order to perform project risk management effectively, the organization or the department must know the meaning of the risk clearly. With regards to a project, the management must focus on the potential effects on the objectives of the project, for example, cost and time (Loosemore, Raftery and Reilly, 2006). Risk is a vulnerability that really matters; it can influence the objectives of the project

Advancing from level 2 to level 3 requires using a risk register. 'The Risk Register is a tool to assist Project Managers in identifying likely sources of risk and the impact they may have on achieving objective. ' (Government office from the North West,2008). The first step is a brainstorm session to identify risk that may affect the project. It is important that the risks are clearly defined so that the risk is understood clearly and can be tackled. Secondly, consequence and probability of risks need to be rated (e.g. 1-5) and define each rating by their impact or likelihood. Finally, multiply the ratings of consequence and impact, rank the risks from highest severity to lowest severity. (Government office from the North West,2008). Every risks should be assigned to a risk owner which is responsible for managing the risk, a risk response to minimise both the likelihood and impact of the risk and a target completion date for the mitigation. Regular risk reviews need to be done because risks might emerge or become no longer relevant constantly. However, the impact

This assignment is included in the 2014 session of the Risk Management module of the MSc in Project Management course at University of Aberdeen. The main purpose of the assignment is to demonstrate my understanding of the issues involved in Risk Management and how they are applied in my current Project environment. The assignment is split in to two questions as detailed below.