Visualization of Defect Inflow and Resolution Cycles: Before, During and After Transfer

Jabangwe, Ronald; Petersen, Kai; mite, Darja

doi:10.1109/apsec.2013.47

Cited by 7 publications

(19 citation statements)

References 23 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The importance and usefulness of the mitigation practices that are presented in this present study have been noted in studies on other GSD contexts as success or critical factors (e.g., the studies by Moe et al (2014), Jabangwe et al (2013), and by da Silva et al (2010)). Thus, the findings of this study shows the relevance of the factors in a distributed development context with offshore outsourcing vendors.…”

Section: Implications For Practicesupporting

confidence: 62%

Distributed software development in an offshore outsourcing project: A case study of source code evolution and quality

Jabangwe

Šmite

Hessbo

2016

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

Context: Offshore outsourcing collaborations can result in distributed development, which has been linked to quality-related concerns. However, there are few studies that focus on the implication of distributed development on quality, and they report inconsistent findings using different proxies for quality. Thus, there is a need for more studies, as well as to identify useful proxies for certain distributed contexts. The presented empirical study was performed in a context that involved offshore outsourcing vendors in a multisite distributed development setting.Objective: The aim of the study is to investigate how quality changes during evolution in a distributed development environment that incurs organizational changes in terms of number of companies involved.Method: A case study approach is followed in the investigation. Only post-release defects are used as a proxy for external quality due to unreliable defect data found pre-release such as those reported during integration. Focus group meetings were also held with practitioners.Results: The results suggest that practices that can be grouped into product, people, and process categories can help ensure post-release quality. However, postrelease defects are insufficient for showing a conclusive impact on quality of the development setting. This is because the development teams worked independently as isolated distributed teams, and integration defects would help to better reflect on the impact on quality of the development setting.Conclusions: The mitigation practices identified can be useful information to practitioners that are planning to engage in similar globally distributed development projects. Finally, it is important to take into consideration the arrangement of distributed development teams in global projects, and to use the context to iden- tify appropriate proxies for quality in order to draw correct conclusions about the implications of the context. This would help with providing practitioners with wellfounded findings about the impact on quality of globally distributed development settings.

show abstract

Section: Implications For Practicesupporting

confidence: 62%

Distributed software development in an offshore outsourcing project: A case study of source code evolution and quality

Jabangwe

Šmite

Hessbo

2016

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

show abstract

“…As shown in Figure 2, the method was first applied in two separate empirical studies (i.e., [3] and [18]). The method was then modified based on the experience and lessons from applying it in the two studies.…”

Section: Research Approachmentioning

confidence: 99%

“…The method was first applied in two separate studies (see [3] and [18]). The case company was Ericsson, a multinational telecommunication corporation.…”

Section: Main Eventsmentioning

confidence: 99%

“…The method is based on lessons from empirical studies presented in [3,16,18] and [19], and the data collection methods for each study are presented in detail in each study. Included in the present paper, apart from the complete method, are details of how the method was developed and how it was refined, as well as how the lessons learned from each individual empirical study helped in the development of the method.…”

Section: Introductionmentioning

confidence: 99%

“…We, therefore, gained insights through the individual studies, and this enabled us to construct a systematic and coherent method by following a method engineering approach. Therefore, the current version of the method presented in this paper is a synthesis and aggregation of lessons learned from GSD empirical studies presented in [3,16,18] and [19]. Although we do not invent the method fragments and the fundamental properties of the method (e.g., the importance of understanding context and the goal-oriented approach), the novelty of the method is in how it combines them into a coherent structure and the insights that are obtained in following the method.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A method for investigating the quality of evolving object‐oriented software using defects in global software development projects

Jabangwe

Wohlin

Petersen

et al. 2016

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

Context: Global software development (GSD) projects can have distributed teams that work independently in different locations or team members that are dispersed. The various development settings in GSD can influence quality during product evolution. When evaluating quality using defects as a proxy, the development settings have to be taken into consideration. Objective: The aim is to provide a systematic method for supporting investigations of the implication of GSD contexts on defect data as a proxy for quality. Method: A method engineering approach was used to incrementally develop the proposed method. This was done through applying the method in multiple industrial contexts and then using lessons learned to refine and improve the method after application. Results: A measurement instrument and visualization was proposed incorporating an understanding of the release history and understanding of GSD contexts. Conclusion: The method can help with making accurate inferences about development settings because it includes details on collecting and aggregating data at a level that matches the development setting in a GSD context and involves practitioners at various phases of the investigation. Finally, the information that is produced from following the method can help practitioners make informed decisions when planning to develop software in comparable circumstances. and multivariate analysis. This analysis approach can be compared with combining the measures in visualization approaches. This is because both approaches can be used to assess the existence of a relationship between either the measures themselves (e.g., quality measures and product modification measures), or the measures and the events in the development setting. Phase 4: evaluation (of quantitative data analysis results given the context)The purpose of Phase 4 is to get deeper insights and explanations about the changes in defects and measures that influence or is linked to defects. During this phase, the GSD context and events in the Figure 5. An example of how to visualize data. Exploring the implication on quality of distributed development and changes in number of companies involved in development activities, across releases. GSD-QuID, global software developmentquality investigation using defects. 636 RONALD JABANGWE ET AL.

show abstract

A Researcher’s Experiences in Supporting Industrial Software Process Improvement

Petersen

2016

Managing Software Process Evolution

View full text Add to dashboard Cite

Visualization of Defect Inflow and Resolution Cycles: Before, During and After Transfer

Cited by 7 publications

References 23 publications

Distributed software development in an offshore outsourcing project: A case study of source code evolution and quality

Distributed software development in an offshore outsourcing project: A case study of source code evolution and quality

A method for investigating the quality of evolving object‐oriented software using defects in global software development projects

A Researcher’s Experiences in Supporting Industrial Software Process Improvement

Contact Info

Product

Resources

About