This document discusses different risk treatment methods in project management. It explains the concepts of avoidance, reduction, transference, and acceptance of risks.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Running head: RISK TREATMENT METHODS Risk Treatment Methods Name of the Student Name of the University Author’s note
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
1RISK TREATMENT METHODS 1. The risk treatment method is defined as avoidance. The lead of the development team has taken the risk treatment method to avoid the scenario of risk. The lead of development team should avoid the use of application development should avoid the development of the application over the Windows phones (Ahmed and Matulevičius 2014). This would help in saving a considerable amount of time based on developing the application with the available APIs and commercial plugins. Without the development of the application, the project team would be able to focus over the Android and iOS platforms. This would be helpful for the team to save time and money required for the project. 2. When a section of the project would become too difficult to perform, the project manager and other teams involved within the project should make use of the reduction technique. Within this technique, the practice of mitigation of the risks would be defined. This technique of mitigation of risks would help the project team to decide on the best form of strategies that would be helpful for the team to mitigate the risk scenarios (Islam, Mouratidis and Weippl 2014). The company should also invest more over the project. This would be helpful for the project team to plan for appropriate steps. These steps should again be approved by the higher managerial levels in order to start over the project. 3. The defined case can be described as a technique of transference. The risk management strategy based on transference is a common method within the risk management program. In this technique of risks management program, the risks would be transferred to a third party service provider or an application. With the help of a third party service provider who would write the code for a software, the project management team could help in transferring the risks based on finding errors within the code (Albakriet al.2014). This third party would be responsible for the management of risks, which could also be in the form of an additional training. Insurance can
2RISK TREATMENT METHODS also be discussed as a good example for transferring the risks. Based on the method of risk transference, it would be the responsibility of the insurance company to take measures based on the risks. 4. Based on the methods of avoidance of risks, the project team should be able to change plans in order to avoid the risk scenarios. In this method of risk treatment, the project team should be able to change the plan for the project (Belkhamza and Wafa 2014). The project team should also be able to schedule the training for the project team based on thinking over methods of risk avoiding. Based on the method of risk acceptance, it can be discussed that this technique could be approached based on identifying the risks (Lucianoet al.2014). The project team should log in to the risk management software without taking any kind of action. The team should accept the risks as it would happen and then decide to deal with the risks.
3RISK TREATMENT METHODS References Ahmed, N. and Matulevičius, R., 2014. Securing business processes using security risk-oriented patterns.Computer Standards & Interfaces,36(4), pp.723-733. Albakri, S.H., Shanmugam, B., Samy, G.N., Idris, N.B. and Ahmed, A., 2014. Security risk assessmentframeworkforcloudcomputingenvironments.SecurityandCommunication Networks,7(11), pp.2114-2124. Belkhamza, Z. and Wafa, S.A., 2014. The role of uncertainty avoidance on e-commerce acceptance across cultures.International Business Research,7(5), p.166. Islam, S., Mouratidis, H. and Weippl, E.R., 2014. An empirical study on the implementation and evaluation of a goal-driven software development risk management model.Information and Software Technology,56(2), pp.117-133. Luciano,C.,Valdivia‐Salas,S.,Ruiz,F.J.,Rodríguez‐Valverde,M.,Barnes‐Holmes,D., Dougher, M.J., López‐López, J.C., Barnes‐Holmes, Y. and Gutierrez‐Martínez, O., 2014. Effects of an acceptance/defusion intervention on experimentally induced generalized avoidance: A laboratory demonstration.Journal of the Experimental Analysis of Behavior,101(1), pp.94-111.