This report analyses the relationship between risk management and the success and failure of software development projects. Subsequently, the report studies the integrity of the knowledge that risk management is based upon. The analysis is supported by two case studies, the “Public Record Office’s Electronic Catalogue” and “Britain’s Training Programme for the Unemployed IT System.”
Software development projects have a long history of failing due to numerous factors. such as bad design, poor resource allocation, lack of communication, software bugs and risk management; The latter being the focus of this report. Jiang and Klein (1999) find that different types of risks will affect budget, user satisfaction and system performance. Other studies indicate that 15 to 35% of all software development projects are cancelled and the remaining projects suffer from schedule slippage, feature creep, expenditure issues or failure to meet their project goals (Boehm, 1991).
The relationship between risk management and the success and failure of a software development project is very important and has gained an increasing amount of interest over the years.
During a software development project, methodologies are applied in an attempt to manage risk by gathering and evaluating information using a structured process. The assumption that a good risk management methodology will reduce software development risks enough to prevent failure is true to an extent. However, problems may arise if, for whatever reason, the software development project does not adhere to traditional approaches.
Read the rest of my report here.
Related Posts
Related posts brought to you by Yet Another Related Posts Plugin.
Leave Your Response