Advancing Risk and Value Management Practices for Processes and Products (original) (raw)

Implementing a Value-Based Approach to Software Process and Product Assessment

Icsoft, 2007

This study tries to advance and define the concepts, principles and practical methods of a valuebased approach, involving definition of the essential concepts of value, cost and worth in software development. These definitions originate from the Value Engineering (VE) method, originally applied and developed for the needs of the production industry. Therefore, for the purposes of this study these concepts are firstly justified and secondly defined. In order to study and evaluate the value-based approach, a method called value assessment is developed and used when assessing processes and products. The results of industrial case show that even though there is still much to do in making the economic-driven view complete in software engineering, the value-based approach outlines a way towards a more comprehensive understanding of it. For industrial users value assessment seems to give a practical help for handling cost and profitability related challenges.

Role of Risk Management in Development of Software Projects

International journal of engineering research and technology, 2014

Nowadays, software development is becoming a major part of enterprise business. Software development is an activity connected with new technologies and high level of knowledge. There are many risks associated with software development such as time-to-market, budget and schedule estimation, product deployment or maintenance. These risks on software development projects must be successfully mitigated to build successful software systems in the organization. Lack of knowledge about risk management is one of the major causes for project failures. To develop a project successfully, risk management determines common risk impact areas in the software projects. Software risk management is a systematic way to manage risks in development of software projects. This paper recognizes the role of risk management in present software projects and aims at providing more support in this area. Firstly the paper consist what are the software risks involved in development of software projects, then a model of software risk management process with the overview of risk assessment process.

Towards a value-based approach in software engineering

Proceedings of the 2nd Wseas International Conference on Computer Engineering and Applications, 2008

The number of companies producing software has grown constantly, and it seems that we need software more and more everyday. Lately, several authors have discussed about the importance of cost efficiency and value creation in software development as well in software process and product improvement (SPI). It also seems that several companies have noticed that competition is increasing and cost-efficient companies have perhaps more competitive advantage in global markets than ever. This study discusses about the concepts, principles and practical methods of economic-driven software engineering and outlines us to understand better the content of value-based approach. This is done in part by presenting a conceptual analysis of the economic-driven view of software development including cost estimation and cost accounting and in part by discussing the costefficiency and value characteristics of software processes, products and their improvement. As a summary this study proposes to use value-based approach to find solutions for cost efficiency related challenges. As well it encourages both technical and economical sciences to work together when creating meaningful and practical solutions for our everyday use.

Managing Requirements Risks: A Value-Based Process

Advances in Risk Management, 2010

The technological, cost, people and schedule issues faced during software development, make it vulnerable for several types of risks. The requirements' related risks are one of the most occurring risks. If remain unnoticed or unmanaged, the requirements related risks can cost a project greatly, financially and otherwise. It is extremely important to manage requirements related risks efficiently and effectively. Moreover, a project can never be successful if stakeholders do not get their "valued" things. Every requirement contributes towards some value for stakeholder(s). Therefore it is important to manage requirements risks to the satisfaction of stakeholders. Different stakeholders have different perception of risk, it is therefore necessary to have a process that not only manages requirements' risks but it also fulfills the values of stakeholders as well. This chapter presents a Value-Based Requirements Risk Management (VRRM) process that is designed to manage requirements related risks in a value based manner.

An industrial case study of implementing software risk management

ACM SIGSOFT Software Engineering Notes, 2001

Explicit risk management is ga ining ground in industrial software development projects. However, there are few empirical studies that investigate the transfer of explicit risk management into industry, the adequacy of the risk management approaches to the constraints of industrial contexts, or their cost-benefit. This paper presents results from a case study that introduced a systematic risk management method, namely the Riskit method, into a large German telecommunication company. The objective of the case study was (1) to analyze the usefulness and adequacy of the Riskit method and (2) to analyze the cost-benefit of the Riskit method in this industrial context. The results of (1) also aimed at improvement and customization of the Riskit method. Moreover, we compare our findings with results of previous case studies to obtain more generalized conclusions on the Riskit method. Our results showed that the Riskit method is practical, adds value to the project, and that its key concepts are understood and usable in practice. Additionally, many lessons learned are reported that are useful for the general audience who wants to transfer risk management into new projects.

IJERT-Role of Risk Management in Development of Software Projects

International Journal of Engineering Research and Technology (IJERT), 2014

https://www.ijert.org/role-of-risk-management-in-development-of-software-projects https://www.ijert.org/research/role-of-risk-management-in-development-of-software-projects-IJERTV3IS041686.pdf Nowadays, software development is becoming a major part of enterprise business. Software development is an activity connected with new technologies and high level of knowledge. There are many risks associated with software development such as time-to-market, budget and schedule estimation, product deployment or maintenance. These risks on software development projects must be successfully mitigated to build successful software systems in the organization. Lack of knowledge about risk management is one of the major causes for project failures. To develop a project successfully, risk management determines common risk impact areas in the software projects. Software risk management is a systematic way to manage risks in development of software projects. This paper recognizes the role of risk management in present software projects and aims at providing more support in this area. Firstly the paper consist what are the software risks involved in development of software projects, then a model of software risk management process with the overview of risk assessment process.

Software Risk Management: a Process Model and a Tool

IFIP International Federation for Information Processing, 2006

This paper is concerned with the risks associated with the software development process. A model {GRisk-Model) is proposed for the management of such risks and a software tool (GRisk-Tool), developed to support the model, is described. Both the method and the tool were created with the participation of senior managers and software engineers of software factories. The model and the tool serve as effective instruments for achieving the continuous improvement of software processes and products.

Risk Management in Software Engineering

Abstract. Software development projects are subject to risks like any other project. These risks must be managed in order for the project to succeed. Current frameworks and models for risk identification , assessment and management are static and unchanging. They lack and cannot adapt to future changes in risk events of decision, developed during the Korean War by fighter pilot Colonel John Boyd, is a dynamic risk management framework that has built in feedback methods and readily adapts to future changes. It can be successfully employed by development teams as an effective risk management framework, helping projects come in on time and on budget

A Framework for Integrating Risk Management into the Software Development Process

Research Journal of Applied Sciences, Engineering and Technology

Software development projects still of high failure rates. Different risk management approaches are recommended by researchers and followed by organizations in order to control this failure rate. Current research is focused towards preventive risk management approach that improves the development process. In this study, we introduce a framework that enhances this approach. This framework describes a systematic method towards enhancing preventive risk management throughout the software development process. In this study, we devised sets of risk management strategies and controls that aim at mitigating each of the identified risks in the adapted list. These strategies besides the identified risk factors are utilized and embedded in the right corresponding Software Development Life Cycle phase to construct our preventive framework.

A Review of Risk Management in Different Software Development Methodologies

Different software development methodologies exist. Choosing the methodology that best fits a software project depends on several factors. One important factor is how risky the project is. Another factor is the degree to which each methodology supports risk management. Indeed, the literature is rich in such studies that aim at comparing the currently available software development process models from different perspectives. In contrast, little effort has been spent in purpose of comparing the available process models in terms of its support to risk management. In this paper, we investigate the state of risk and risk management in the most popular software development process models (i.e. waterfall, v-model, incremental development, spiral, and agile development). This trend in such studies is expected to serve in several aspects. Technically, it helps project managers adopt the methodology that best suits their projects. From another side, it will make a way for further studies that...