Complementing Measurements and Real Options Concepts to Support Inter-iteration Decision-Making in Agile Projects

Agile software projects are characterized by iterative and incremental development, accommodation of changes and active customer participation. The process is driven by creating business value for the client, assuming that the client (i) is aware of it, and (ii) is capable to estimate the business value, associated with the separate features of the system to be implemented. This paper is focused on the complementary use of measurement techniques and concepts of real-option-analysis to assist clients in assessing and comparing alternative sets of requirements. Our overall objective is to provide systematic support to clients for the decision-making process on what to implement in each iteration. The design of our approach is justified by using empirical data, published earlier by other authors

How Do Real Options Concepts Fit in Agile Requirements Engineering?

Agile requirements engineering is driven by creating business value for the client and heavily involves the client in decision-making under uncertainty. Real option thinking seems to be suitable in supporting the client’s decision making process at inter-iteration time. This paper investigates the fit between real option thinking and agile requirements engineering. We first look into previously published experiences in the agile software engineering literature to identify (i) ‘experience clusters’ suggesting the ways in which real option concepts fit into the agile requirements process and (ii) ‘experience gaps’ and under-researched agile requirements decision-making topics which require further empirical studies. Furthermore, we conducted a cross-case study in eight agile development organizations and interviewed 11 practitioners about their decision-making process. The results suggest that options are almost always identified, reasoned about and acted upon. They are not expressed in quantitative terms, however, they are instead explicitly or implicitly taken\ud into account during the decision-making process at interiteration time

Value Framing: A Prelude to Software Problem Framing

Software problem framing is a way to find specifications for software. Software problem frames can be used to structure the environment of a software system (the machine) and specify desired software properties in such a way that we can show that software with these properties will help achieve the required effects in the environment. Actually framing a software problem, i.e. finding suitable problem frames of a given situation, is creative activity for which no guidelines are currently known. In this paper, we propose to use an idea exploration technique called e3-value to find software problem frames. The e3-value methodology is an approach to help business analysists solve the problem of designing a networked enterprise, defined as a set of businesses or business units that make money by performing value exchanges over a computer network. The outcome of e3-value is viewed by business managers as a solution, but it is a problem for software engineers who have to implement this idea. In this paper we illustrate the combination of e3-value with problem framing by means of a small example from real life, and discuss the research questions that come out of this

Discovering Strategies to Improve Business Value in Outsourcing Projects

This paper deals with the problem of leveraging client business value in a software development outsourcing relationship. We have observed software development projects from two different Dutch IT outsourcing companies and studied the approach they apply in their (successful) projects. The results show that they create a role dedicated to facilitate communication. This arrangement has the potential to put team members in a better position to communicate, facilitating the transfer of information supporting the rationale behind design decisions. Teams are thus better equipped to anticipate change and to react faster in solving everyday problems. This paper describes our observations and the practical implications we expect, such as the improvement of re-buy intention on the client's side

Estimating, planning and managing Agile Web development projects under a value-based perspective

Context: The processes of estimating, planning and managing are crucial for software development projects, since the results must be related to several business strategies. The broad expansion of the Internet and the global and interconnected economy make Web development projects be often characterized by expressions like delivering as soon as possible, reducing time to market and adapting to undefined requirements. In this kind of environment, traditional methodologies based on predictive techniques sometimes do not offer very satisfactory results. The rise of Agile methodologies and practices has provided some useful tools that, combined with Web Engineering techniques, can help to establish a framework to estimate, manage and plan Web development projects. Objective: This paper presents a proposal for estimating, planning and managing Web projects, by combining some existing Agile techniques with Web Engineering principles, presenting them as an unified framework which uses the business value to guide the delivery of features. Method: The proposal is analyzed by means of a case study, including a real-life project, in order to obtain relevant conclusions. Results: The results achieved after using the framework in a development project are presented, including interesting results on project planning and estimation, as well as on team productivity throughout the project. Conclusion: It is concluded that the framework can be useful in order to better manage Web-based projects, through a continuous value-based estimation and management process.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-

A Conceptual Model of Client-driven Agile Requirements Prioritization: Results of a Case Study

ABSTRACT Requirements (re)prioritization is an essential mechanism of agile development approaches to maximize the value for the clients and to accommodate changing requirements. Yet, in the agile Requirements Engineering (RE) literature, very little is known about how agile (re)prioritization happens in practice. Conceptual models about this process are missing, which, in turn, makes it difficult for both practitioners and researchers to reason about requirements decision-making at inter-iteration time. We did a multiple case study on agile requirements prioritization methods to yield a conceptual model for understanding the inter-iteration prioritization process. The model is derived by using interview data from practitioners in 8 development organizations. Such a model makes explicit the concepts that are used tacitly in the agile requirements prioritization practice and can be used for structuring future empirical investigations about this topic, and for analyzing, supporting, and improving the process in real-life projects

Costs, Benefits and Value Distribution – Ingredients for Successful Cross-Organizational ES Business Cases

This paper introduces my PhD research project on developing guidelines for creating successful business cases for Enterprise System implementations in network settings. Three important aspects that were found to be important in such business cases are: the costs, benefits and the value distribution within a network. Each of the three aspects is addressed in this paper and the relationships between them are pointed out. A research model is presented showing how all three aspects contribute to the main goal of defining successful business case guidelines

Business Value Is not only Dollars - Results from Case Study Research on Agile Software Projects

Business value is a key concept in agile software development. This paper presents results of a case study on how business value and its creation is perceived in the context of agile projects. Our overall conclusion is that the project participants almost never use an explicit and structured approach to guide the value creation throughout the project. Still, the application of agile methods in the studied cases leads to satisfied clients. An interesting result of the study represents the fact that the agile process of many projects differs significantly from what is described in the agile practitioners’ books as best practices. The key implication for research and practice is that we have an incentive to pursue the study of value creation in agile projects and to complement it by providing guidelines for better client’s involvement, as well as by developing structured methods that will enhance the value-creation in a project