Hybrid Software Development Approaches in Practice: A European Perspective

Agile and traditional development approaches are used in combination in todays software development. To improve the understanding and to provide better guidance for selecting appropriate development approaches, it is important to analyze such combinations in practice. Results obtained from an online survey strongly confirm that hybrid development approaches are widely used in industry. Our results show that hybrid development approaches: (i) have become reality for nearly all companies; (ii) are applied to specific projects even in the presence of company-wide policies for process usage; (iii) are neither planned nor designed but emerge from the evolution of different work practices; and, (iv) are consistently used regardless of company size or industry secto

<i>Trace++</i>: A Traceability Approach for Agile Software Engineering

Agile methodologies have been introduced as an alternative to traditional software engineering methodologies. However, despite the advantages of using agile methodologies, the transition between traditional and agile methodologies is not an easy task. There are several problems associated with the use of agile methodologies. Examples of these problems are related to (i) lack of metrics to measure the amount of rework that occurs per sprint, (ii) interruption of a project after several iterations, (iii) changes in the requirements, (iv) lack of documentation, and (v) lack of management control. In this paper we present Trace++, a traceability technique that extends traditional traceability relationships with extra information in order to support the transition between traditional and agile software development. The use of Trace++ has been evaluated in two real projects of different software development companies to measure the benefits of using Trace++ to support agile software development

Intangible trust requirements - how to fill the requirements trust "gap"?

Previous research efforts have been expended in terms of the capture and subsequent instantiation of "soft" trust requirements that relate to HCI usability concerns or in relation to "hard" tangible security requirements that primarily relate to security a ssurance and security protocols. Little direct focus has been paid to managing intangible trust related requirements per se. This 'gap' is perhaps most evident in the public B2C (Business to Consumer) E- Systems we all use on a daily basis. Some speculative suggestions are made as to how to fill the 'gap'. Visual card sorting is suggested as a suitable evaluative tool; whilst deontic logic trust norms and UML extended notation are the suggested (methodologically invariant) means by which software development teams can perhaps more fully capture hence visualize intangible trust requirements

AGILE ADOPTION IN INVESTMENT BANKS

Many companies and organizations, regardless of industries, countries, size, and cultures, are in the process of transiting from traditional project management methods to Agile. When it comes to financial industry, today’s investment banks, face more unstable market conditions, faster changes of worldwide politics, economies and technologies, stricter regulations, and greater pressure to meet customers’ requirements and sustain revenue growth. Investment banks are usually full-service global financial institutions, which provide advisory and financing banking services, as well as sales, market making, and research on financial products. Therefore, investment banks are in great need to transform from traditional PM concepts to Agile. However, a big issue in investment banks is the lack of applying Agile. To address this issue, this thesis is focusing on “what is the current status of adopting Agile in investment banks”, “why investment banks have not fully adopted Agile”, “why investment banks should adopt Agile methodology” and “how to apply agile in investment banks”. The research of this thesis will be conducted using two main approaches. To answer the first three questions mentioned above, two main approaches, researching the existing articles and questionnaire survey among the investment banks employees, will be used. Based on the findings and conclusions of the research and the survey, recommendations will be provided to address how investment banks can successfully apply Agile within the organization. The results of the research will be able to provide a guidance for investment banks on how to smoothly transit from traditional project management methods to Agile, and help to bring more attention to this topic and stimulate more related research in the future

Are Delayed Issues Harder to Resolve? Revisiting Cost-to-Fix of Defects throughout the Lifecycle

Many practitioners and academics believe in a delayed issue effect (DIE); i.e. the longer an issue lingers in the system, the more effort it requires to resolve. This belief is often used to justify major investments in new development processes that promise to retire more issues sooner. This paper tests for the delayed issue effect in 171 software projects conducted around the world in the period from 2006--2014. To the best of our knowledge, this is the largest study yet published on this effect. We found no evidence for the delayed issue effect; i.e. the effort to resolve issues in a later phase was not consistently or substantially greater than when issues were resolved soon after their introduction. This paper documents the above study and explores reasons for this mismatch between this common rule of thumb and empirical data. In summary, DIE is not some constant across all projects. Rather, DIE might be an historical relic that occurs intermittently only in certain kinds of projects. This is a significant result since it predicts that new development processes that promise to faster retire more issues will not have a guaranteed return on investment (depending on the context where applied), and that a long-held truth in software engineering should not be considered a global truism.Comment: 31 pages. Accepted with minor revisions to Journal of Empirical Software Engineering. Keywords: software economics, phase delay, cost to fi

E-finance-lab at the House of Finance : about us

The financial services industry is believed to be on the verge of a dramatic [r]evolution. A substantial redesign of its value chains aimed at reducing costs, providing more efficient and flexible services and enabling new products and revenue streams is imminent. But there seems to be no clear migration path nor goal which can cast light on the question where the finance industry and its various players will be and should be in a decade from now. The mission of the E-Finance Lab is the development and application of research methodologies in the financial industry that promote and assess how business strategies and structures are shared and supported by strategies and structures of information systems. Important challenges include the design of smart production infrastructures, the development and evaluation of advantageous sourcing strategies and smart selling concepts to enable new revenue streams for financial service providers in the future. Overall, our goal is to contribute methods and views to the realignment of the E-Finance value chain. ..

Agile software development in a context of plan-based organizations

Agile software development has increasingly been used in the last fifteen years with the goal of improving traditionally time-consuming and rather non-user friendly process of developing software code. As implications of agile development and its impact on employees are still unclear, it is important to understand the benefits, opportunities and limitations of this development or collaboration mechanism. Thus, empirical evidence with implications for decision makers in the field of corporate policy and software development is an open research field. This master thesis analyzes the potentials of agile software development and how this approach can be used to support the development processes in companies, in terms of efficiency, shorter time-to-market as well as better customer fit of the developed products or services. By exploring some of the key features of different methods and processes, the potentials and limitations of the selected approaches are analyzed and linked to recent literature insights