Software development risk management model

Abstract

Every software project by its inherent nature is unique and contains significant numbers of uncertainties from various perspectives such as time-to-market, budget and schedule estimation, product deployment or maintenance. If failing to control these uncertainties, it imposes potential risks not only during the development phases but also throughout the life cycle of the product. Software risk management is an effective tool to control these risks and contributes to increase the likelihood of project success. Risk management needs to be integrated as early as possible from a holistic perspective into the development. However a comprehensive risk management practice is not always possible due to resource problems, more emphasize on budget and schedule constraints and difficulties to concretely estimate the benefit of risk management.This thesis proposes a Goal-driven Software Development Risk Management Model (GSRM) that explicitly integrates into the requirements engineering phase. The integration provides an early warning of potential problems so that both preventive and corrective actions can be undertaken to avoid the causes of project failure. The framework is comprised of four layers, i.e., goal, obstacle, assessment and treatment, that support the identification, assessment, treatment and documentation of risks in relation to project-specific goals. GSRM is implemented in active on-going software development projects to empirically evaluate its usefulness, particular advantages and limitations in an industrial context. The results show that goaldriven approach is suitable for risk management and risk management is well integrated into requirements engineering phase. It is not always necessary to rank budget and schedule related goals and risk factors at the highest priority for risk management. At the early stage of the project risk factors related to estimation, project management, project scope, requirements, change management and human (i.e. customer/user and practitioner) and at the later stage risk factors related to user satisfaction and product usage are more frequent and severely affect meeting the project goals. If project risk factors are beyond the control of a project manager and project development environment, it is difficult to control the risks. The results conclude that early risk management practice is necessary and GSRM contributes to this direction for a successful project outcome. ZusammenfassungJedes Software-Entwicklungsprojekt ist einzigartig und geprägt von schwer planbaren Einflussfaktoren, wie time-to-market oder Budget, aber auch von Einflüssen resultierend aus der Integration und der Wartung. Die Beherrschung dieser Einflussgrößen ist unabdingbar für die Minimierung der Risiken während der Entwicklung als auch während des gesamtem Software-Lebenszyklus.

Agile risk management using software agents

“…Human resource Formation of team, where team was being organized without considering their necessary skills and knowledge Multiple responsibilities where one team member is responsible for many tasks Some developers are not aware of the benefits of applying agile methods, and so are reluctant to apply agile practices Lack of accountability where team members do not take responsibility for any delayed task coupled with a lack of supervision Collaboration between team members is difficult, especially when they are not located together Structured development process Scrum meetings; daily scrum, sprint planning and sprint review meetings are sometimes inefficient where they are being held too often, or taking up too much time or setting up the meeting is difficult Difficulties in estimating project work on legacy code Environmental Poor customer involvement and unclear product requirements Individual contribution is not recognized and no guidelines exist in determining accurate measurement of individual performance Information systems and technology A lack of communication between team members that are co-located causes duplication in resolving problems Newly hired team members tend to create code errors due to unfamiliarity with the software software development risk management model (GSRM) proposed by Islam (2009) was reused. This model is used to specify the input for the project, which consists of the type of risks and the risk indicators as well as the environment data which can be used to identify the risks for the project.…”

Managing Risks in the System Analysis and Requirements Definition Phase

“…Shareef Islam [17] proposed Software Development Risk Management Model-a goal-driven approach, the author's proposed common project riskiness factors as shown in figure 1.…”

“…List of risk event and associated factors that Shareef Islam [17] proposed shown in Table 2. Determining the project risk factors is not an easy task due to the nature of the project.…”

“…Determining the project risk factors is not an easy task due to the nature of the project. Shareef Islam [17] developed a model and determined the project risks based on the project benefits at the end. As Shareef Islam [17] claimed that every project has a common goal to not lose any money.…”

“…Shareef Islam [17] developed a model and determined the project risks based on the project benefits at the end. As Shareef Islam [17] claimed that every project has a common goal to not lose any money. Therefore, the author decided how risky the project is in terms of cost, schedule and other related factors as well as shown in table 2.…”