Module 4 - SLP
Alexander Evans
ITM423
June 5, 2016
Professor Jose Angeles
Module 4 - SLP
In keeping with the course long SLP project we now have the opportunity of putting all of the previous SLP course work into play. The general project of the SLP assignments has been creating an implementation plan for learning software for the Trident University Website. The products being examined are from Desire2Learn (D2L). The previous SLP’s gave us the opportunity to review some of the project management software and now we will piece what we have learned together and put together a plan for actually using it.
To begin the project implementation a thorough risk management system will need to be put in place in order to be able to mitigate any possible downtime due to any unforeseen issues that could potentially bring the project to a halt. In order for us to accurately assess and process a usable risk management system, the project manager will need to have a good understanding of all areas of the project, meet with stakeholders, developers, the project team, and any other parties involved to work out defined requirements and any limitations that the new software will not be able to deliver. In addition to this plan all relevant documents to the project should be reviewed for errors, and any contingency plans that need to be made will be discussed also. It is important for all parties involved in the project have at least one representative present during the 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.
The risk-management plan then starts by identifying each of these sources, their magnitude, their relation to the various design stages, and their possible effects on cost, schedule, quality, and performance. The next step is to look for modifications or alternatives that would permit risk reduction. The thoughtful selection of computer language or operating system may reduce some of the integration risks. If management decides to develop a new software package, contingency plans that cut expenses and development time at the cost of lower performance should be prepared. These plans are used in case the undesired event takes place. By preparing a contingency plan in advance, time is
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
All efforts will be made by the Project Manager to plan for and handle any risks. Continual risk monitoring will be done by the project manager throughout the projects duration.
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
Risk or threat is common and found in various fields of daily life and business. This concept of risk is found in various stages of development and execution of a project. Risks in a project can mean there is a chance that the project will result in total failure, increase of project costs, and an extension in project duration which means a great deal of setbacks for the company. The process of risk management is composed of identifying, assessing, mitigating, and managing the risks of the project. It
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.
Risk management is an ongoing process that must continue through the life of a project. It includes processes for risk management planning, identification, analysis, monitoring, and control. These processes need to be reviewed throughout the project’s lifecycle as new risks arise throughout the implementation of the project. It is the objective of risk management to decrease the probability and impact of events adverse to the project. On the other hand, any event that could have a positive impact should be exploited.
* Any identifiable obstacles and risks (threats) that might prevent the successful attainment of the project goals must be considered. Each risk must be analyzed, quantified, and prioritized as much as possible with the information available at this stage of a new project. Risk responses, including mitigations, risk sharing, risk avoidance, and risk tolerances should be described in this portion of the project proposal.
For example, in the building alterations, the tasks and the cost could be outlined with a quantitative modeling method. As well as a qualitative method, that includes a matrix, which will assist in developing risk responses that will be effective in mitigating possible risk. When a part was needed for a project deciding if it would be more economical to purchase or make the part. When presented with numerical data with cost, life cycle, and maintenance cost for up keep on two or more products that achieve the same goal. A risk management plan could be used to help access and handle project related risks. As for the risk tree, it could be used to help the project team decide on what the best option is for a task by giving a visual representation of the if then relationships in terms of
The Project Manager and the Lead designer and Lead Engineer will be in charge of the risk management plan. The program manager will monitor the project risks and enforced mitigation strategies. The Lead Developers will implement and monitor the strategies to control technological risks that could affect
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
When dealing with new technologies, historical information may not serve as a primary evaluation tool since completely new risks will likely arise. It is still important to review the existing information and the lessons learned, since they will provide first hand guidance on the company’s risk tolerance, effective responses used and the past project resources familiar and experienced with risk management practices. This information is important when selecting the project team members; all team members should be prepared, know what to do when a crisis occurs and provide an agile response in accordance to the project risk management plan.
The project manager working with the project team and project client will ensure risks are actively identified, analyzed and managed throughout the life of the project. Risks will be identified as early as possible to minimize their impact. This can be done using several ways like