Software and system development faces numerous challenges of rapidly changing markets. To address such challenges, companies projects design adopt specific approaches by combining well-structured comprehensive methods flexible agile practices. Yet, the number practices is large, available studies argue that actual process composition carried out in a fairly ad-hoc manner. The present paper reports on survey hybrid software approaches. We study which are used practice, how different combined,...

The surveyed companies applied hybrid development approaches to specific projects even when company-wide policies for process usage existed. These emerged from the evolution of different work practices and were consistently used regardless company size or industry sector.

Background: Agile software development has been increasingly adopted during the last two decades. Nonetheless, many studies show that using agile methods as defined in literature does not work very well. Thus, companies adapt these by just parts of them (called practices). Objective: The goal study was to understand which practices are used industry under different circumstances, such project types, domains, or processes. Method: We conducted a mapping empirical industry. search strategy...

Software process improvement (SPI) has been around for decades: frameworks are proposed, success factors studied, and experiences have reported. However, the sheer mass of concepts, approaches, standards published over years overwhelms practitioners as well researchers. What is out there? Are there new trends emerging approaches? open issues? Still, we struggle to answer these questions about current state SPI related research. In this article, present results from an updated systematic...

Context: In agile transformations there are many challenges. One very important but less considered and treated in research cultural challenges associated with an mindset. Although shows that clashes general organizational resistance to change part of the most significant adoption barriers. Objective: We identify arise from interplay between culture culture. doing so, we tackle this field come up contributions for further regarding a problem practitioners face today. Method: This is done...

Context: In agile transformations, there are many challenges such as alignment between practices and the organizational goals strategies or issues with shifts in how work is organized executed. One very important challenge but less considered treated research cultural associated an mindset. Although shows that clashes general resistance to change part of most significant adoption barriers. Objective: We identify arise from interplay culture culture. doing so, we tackle this field come up...

Software process improvement (SPI) is around for decades: frameworks are proposed, success factors studied, and experiences have been reported. However, the sheer mass of concepts, approaches, standards published over years overwhelms practitioners as well researchers. What out there? Are there new emerging approaches? open issues? Still, we struggle to answer question what current state SPI related research? In this paper, present initial results from a systematic mapping study shed light...

Abstract Many smaller companies cannot afford the time and effort to change their development processes all at once. In some cases, are not aware of fact that many aspects agile already in place. The aim this work was evaluate if an evolutionary transition software is suitable for small companies. We conducted a case study with company start step‐by‐step transition. Initially, three practices were introduced. Based on assessment improvements, continued Kanban practices. Experiences...

Context: Agile on team level is already understood. For scaling Agile, many different frameworks exist, but only few are actually used. Selection often not done systematically, based popularity of the framework or recommendation consultants. Objective: An informed decision-support needed, which to choose. Method: A literature review and several workshops were conducted identify existing suitable criteria compare them. Results: We present a set most one. Our approach select appropriate...

Background: Technology transfer is one key to the success of research projects, especially in Software Engineering, where (practical) impact outcome may depend not only on reliability and feasibility technologies, but also their applicability industrial settings. However, there limited knowledge current state practice how assess technology transfer. Objective: We aim at elaborating a set hypotheses takes place Engineering projects. Method: designed an exploratory survey with participants two...

For decades, Software Process Improvement (SPI) programs have been implemented, inter alia, to improve quality and speed of software development. To set up, guide, carry out SPI projects, measure state, impact, success, a multitude different approaches considerable experience are available. addresses many aspects ranging from individual developer skills entire organizations. It comprises for instance the optimization specific activities in lifecycle as well creation organization awareness...

Abstract It is commonly known that software or system development processes are very important for getting a high‐quality product. Such can be described in many different ways, from textual documents to existing modeling notations. Before dealing with the overall goal of improving description processes, this paper evaluates current state practice regarding process descriptions and reasons that. A major focus on degree formality. Based an interview guideline, series 12 interviews was...

Because agile development has become more important in software engineering recent years, many companies want to agile. One way do so is context-specific improvement, preferably performed by selecting the right practices and integrating them into current process. For making an appropriate selection, impact on improvement goals needs be known. Therefore, idea build overall model that includes of at least most commonly used practices. This mainly built these practices, various characteristics,...

[Background] The effort required to systematically collect historical data is not always allocable in agile processes and management usually delegated the developers' experience, who need remember previous project details. However, even if well trained, developers cannot precisely a huge number of details, resulting wrong decisions being made during development process. [Aims] goal this paper operationalize Experience Factory an way, i.e., defining strategy for collecting using approach....

Background: Particularly during and after research projects, technology transfer into practice plays an important role for academia to get technologies use industry improve their development. Objective: Our goal was gain more current knowledge about how from software engineering (SE) industrial is accomplished best measure the effectiveness of this transfer. Method: We conducted a study in context two German covering many different organizations academia. Results: This paper presents design...

Abstract The emergence of agile methods and practices has not only changed the development processes but might also have affected how companies conduct software process improvement (SPI). Through a set complementary studies, we aim to understand SPI in times development. Specifically, (a) identify characterize publications that connect elements agility SPI, (b) explore which extent methods/practices been used context (c) whether topics addressed literature are relevant useful for industry...