Revised Risk List ( Assignment 3) - Amel94/ITC303-XCoders GitHub Wiki

Revised Risk List Software project risk management in the project Resource Allocation System is crucial part for the software development project. It is used for project planning and control purposes during the project execution. Risk management will help reduce project failure. To manage software project risks, the first step is to identify a list of risks for checklist. To deliver good software risks must be reduced. • Lack of top management commitment to the project • Lack of adequate user involvement • Failure to gain user commitment • Lack of cooperation from users • Changing scope / objectives • Misunderstanding of the requirements • Lack of frozen requirements • Lack of effective project management skill • No planning or inadequate planning • Artificial deadlines • Lack of "people skill" in project leadership • Development of wrong software functions • Continuous requirement changes • Lack of required knowledge or skill • Changes to membership on the project team • Organizational instability • Insufficient resources • Lack of an effective project management methodology • Lack of budget • Lack of time

Identifying and assessing project risks is an essential start-up task. The resulting artifacts will serve as the basis for risk mitigation and the development of iterations in the forthcoming elaboration and construction phases. Identify potential risks that would decrease the likelihood that the development team will be able to deliver the project with the right features, the specified level of quality, on time and within budget. Analyze and prioritize the risks by estimating the impact of each and the likelihood of its occurrence to determine the risk exposure for each risk. Identify risk avoidance strategies to reorganize the project so that you can reduce or eliminate risks. 4. Identify risk mitigation strategies. Identify risk contingency strategies. Revisit risks frequently within iterations and subsequent phases.