Factors influencing code review processes in industry

@article{Baum2016FactorsIC,
  title={Factors influencing code review processes in industry},
  author={Tobias Baum and Olga Liskin and Kai Niklas and Kurt Schneider},
  journal={Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering},
  year={2016}
}
  • T. Baum, Olga Liskin, K. Schneider
  • Published 1 November 2016
  • Business, Computer Science
  • Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering
Code review is known to be an efficient quality assurance technique. Many software companies today use it, usually with a process similar to the patch review process in open source software development. However, there is still a large fraction of companies performing almost no code reviews at all. And the companies that do code reviews have a lot of variation in the details of their processes. For researchers trying to improve the use of code reviews in industry, it is important to know the… 

Figures and Tables from this paper

The Choice of Code Review Process: A Survey on the State of the Practice
TLDR
A survey among commercial software development teams supported many of the stated hypotheses, e.g., that change-based code review is the dominating style of code review in the industry, and that teams doing change- based code review have a lower risk that review use fades away.
Learning as an Outcome of Code Review at Capgemini
Code Review is known to be an efficient technique for finding defects in code. The technique also has other benefits, including the promotion of knowledge sharing, community building, and maintaining
Modern Code Review Benefits-Primary Findings of A Systematic Literature Review
TLDR
The industry can incorporate the MCR process widely, whereas software engineers being aware of the real benefits of MCR can provide their participation effectively in achieving those benefits in reality.
Comparing pre‐commit reviews and post‐commit reviews using process simulation
TLDR
A parametric discrete event simulation model of certain agile development processes is designed and indicates that the best choice does depend on the context but also that there are many situations with no practically relevant difference between both choices.
Test-Driven Code Review: An Empirical Study
TLDR
It is found that most developers prefer to review production code as they deem it more critical and tests should follow from it, and general poor test code quality and no tool support hinder the adoption of TDR.
Code Reviews, Software Inspections, and Code Walkthroughs: Systematic Mapping Study of Research Topics
TLDR
This mapping study illustrates what kinds of research questions are addressed in code review literature by identifying themes emerged from analysis of 75 original articles.
Does Project Associated Situational Factors have Impact on Sustainability of Modern Code Review Workforce?
TLDR
The Systematic Literature Review (SLR) is performed to identify the project-related situational factors that can impact the sustainability of the MCR workforce and will be advantageous for experts involved in situational software engineering research as well as the M CR workforce to sustain for longer by overcoming the challenge of unidentified situations.
Tools, processes and factors influencing of code review
TLDR
This work aims to succinctly describe code review process, giving a framework of the tools and factors influencing code review to aid reviewers and authors in the code review stages and choose the suitable code review tool.
Towards a taxonomy of code review smells
Challenges and Benefits of Modern Code Review-Systematic Literature Review Protocol
TLDR
The aim is to highlight and organize the challenges and benefits regarding modern code review context by providing classified list of challenges andbenefits and to beneficial for software quality assurance practitioners and researchers.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 43 REFERENCES
A Faceted Classification Scheme for Change-Based Industrial Code Review Processes
TLDR
There are many commonalities in the code review processes of these companies, but also a lot of variation in the details, so a simple process taxonomy cannot describe these variations adequately, and so a faceted classification scheme is presented.
Understanding the gap between software process practices and actual practice in very small companies
TLDR
The findings in this study give an insight toward the work products as they relate to software development process practices in very small companies and the important factors that must be considered to assist project success.
Persuading Software Development Teams to Document Inspections: Success Factors and Challenges in Practice
TLDR
Key success factors and challenges were identified in order to explain how the review teams changed their perception throughout the adoption of document inspection.
On the understanding of programs with continuous code reviews
TLDR
It is concluded that there is a clear positive effect on the understandability and collective ownership of the code base with continuous code reviews, but also limiting factors and drawbacks for complex review tasks.
Using grounded theory to understand software process improvement: A study of Irish software product companies
An investigation into software development process formation in software start-ups
TLDR
The results show that the previous experience of the person tasked with managing the development work is the prime influencer on the process a company initially uses.
Factors Contributing to Software Quality Practices - An Australian Case Study
  • L. Land, J. Higgs
  • Business
    2007 International Conference on Wireless Communications, Networking and Mobile Computing
  • 2007
TLDR
The key factors which impact software quality practices in a case study are explored, by studying the perspectives of three key stakeholders - developers, managers and customers, by using the grounded theory approach to develop an initial framework.
Peer reviews in real life - motivators and demotivators
TLDR
The results show that companies that use reviews have adjusted the process for their own needs, and the main motivator for arranging reviews is the decreased amount of defects in products while the other aspects of reviews are not considered as important.
Expectations, outcomes, and challenges of modern code review
TLDR
This study reveals that while finding defects remains the main motivation for review, reviews are less about defects than expected and instead provide additional benefits such as knowledge transfer, increased team awareness, and creation of alternative solutions to problems.
Knowledge Creation In Information Systems Development Teams: The Role Of Pair Programming And Peer Code Review
TLDR
Findings show that the techniques may be substitutes on a dyadic level, but may complement each other regarding their effects on team-level knowledge creation: if applied simultaneously, they may collectively enable socialization, externalization, combination, and internalization of knowledge.
...
1
2
3
4
5
...