Why Good Developers Write Bad Code: An Observational Case Study of the Impacts of Organizational Factors on Software Quality

@article{Lavalle2015WhyGD,
  title={Why Good Developers Write Bad Code: An Observational Case Study of the Impacts of Organizational Factors on Software Quality},
  author={Mathieu Lavall{\'e}e and Pierre N. Robillard},
  journal={2015 IEEE/ACM 37th IEEE International Conference on Software Engineering},
  year={2015},
  volume={1},
  pages={677-687}
}
How can organizational factors such as structure and culture have an impact on the working conditions of developers? This study is based on ten months of observation of an in-house software development project within a large telecommunications company. The observation was conducted during mandatory weekly status meetings, where technical and managerial issues were raised and discussed. Preliminary results show that many decisions made under the pressure of certain organizational factors… 
View on ACM
upedu.org
43 Citations
Highly Influential Citations
6
Background Citations
35
Methods Citations
1
Results Citations
1

Figures and Tables from this paper

43 Citations

Citation Type

Citation Type

Researching Human and Organizational Factors Impact for Decisions on Software Quality
TLDR
Some relevant evidences of the influence of HOF on software quality has been reviewed and analysed to discuss the challenges in this area confirming the need of promoting deeper and wider research efforts.
Can Security Become a Routine?: A Study of Organizational Change in an Agile Software Development Group
TLDR
Interestingly, group members acknowledged an unfulfilled need for change but defended the structure inhibiting change, and security initiatives need to consider this interplay of structure and situated practice, and manage change in addition to providing expertise and tools.
Are We Working Well with Others? How the Multi Team Systems Impact Software Quality
TLDR
It is hypothesized that managers of large software project should identify external teams most likely to interfere with their development work, to appoint brokers to redirect external requests to the appropriate resource, and to ensure that there are opportunities to discuss technical issues at the multi-team level.
Time Pressure in Software Engineering: A Systematic Literature Review
Effects of contextual information on maintenance effort: A controlled experiment
Misaligned values in software engineering organizations
TLDR
The authors' analysis indicated that value misalignment between groups is related to organizational performance and can help to explain why some companies are more efficient than others and point the way to interventions to address organizational challenges.
Identifying ”good” practices of developers using corrective and preventive actions and their impact on software metrics
TLDR
This work presents a literature review, an analysis on how certain actions of software developers impact certain software metrics (such as defect density), and an attempt to highlight good development practices based on the corrective and preventive actions extracted from the literature.
Understanding Technical Debt at the Code Level from the Perspective of Software Developers
TLDR
This paper presents the results of a survey involving 74 participants that work in the Brazilian software industry, in order to understand why technical debt is introduced, eliminated and how it is managed in practice, with a focus on the code level.
An Empirical Evaluation of Software Quality Assurance Practices and Challenges in a Developing Country
  • O. Sowunmi, S. Misra
  • Computer Science
    2015 IEEE International Conference on Computer and Information Technology; Ubiquitous Computing and Communications; Dependable, Autonomic and Secure Computing; Pervasive Intelligence and Computing
  • 2015
TLDR
It was observed that while most practitioners claim to adhere to software quality practices, they barely have an understanding of software quality standards and a vast majority do not have a distinct software quality assurance team to enforce this quality.
Exploring Community Smells in Open-Source: An Automated Approach
TLDR
It is highlighted that community smells are highly diffused in open-source and are perceived by developers as relevant problems for the evolution of software communities, and a number of state-of-the-art socio-technical indicators can be used to monitor how healthy a community is and possibly avoid the emergence of social debt.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 34 REFERENCES
Organizational Factors Shaping Software Process Improvement in Small-Medium Sized Software Teams: A Multi-Case Analysis
  • I. Allison
  • Business
    2010 Seventh International Conference on the Quality of Information and Communications Technology
  • 2010
TLDR
This paper presents an analysis of SPI across six software teams in the UK using a framework based on Giddens’ Structuration Theory to highlight how the context influences the outcome.
The impacts of software process improvement on developers: A systematic review
TLDR
A systematic review on the impacts of Software Process Improvement (SPI) on developers selected 26 studies from the highest quality journals, conferences, and workshop in the field and categorized using the Ishikawa Diagram.
The influence of organisational factors on the success and quality of a product-line architecture
  • C. B. Jaktman
  • Business, Computer Science
    Proceedings 1998 Australian Software Engineering Conference (Cat. No.98EX233)
  • 1998
TLDR
In this work, organisational factors which affect the quality of the code and architecture are found which are typically not documented and found to be influential on the success and quality of a product-line architecture.
Exploring the human and organizational aspects of software cost estimation
TLDR
It is concluded that there are many factors that affect software cost estimation and need to be considered in future research, and a basic taxonomy of attributes is suggested that could be used to structure the many issues involved in and affectingSoftware cost estimation.
Information Needs in Collocated Software Development Teams
TLDR
This work analyzed software developers' day-to-day information needs at a large software company and transcribed their activities in go-minute sessions to identify information types and cataloged the outcome and source when each type of information was sought.
Software Engineering Using RATionale
Organizational Factors for Successful Management of Software Development
  • H. Leung
  • Business
    J. Comput. Inf. Syst.
  • 2002
TLDR
This study focuses on two variables that impact the success of a project: software development management practices and organizational factors, and identifies a list of good management practices adopted in the two regions.
Studying Software Engineers: Data Collection Techniques for Software Field Studies
TLDR
A taxonomy of techniques is provided, focusing on those for data collection, organized according to the degree of human intervention each requires, and a discussion of how to use it effectively is provided.
Maintaining mental models: a study of developer work habits
TLDR
It is found that many problems arose because developers were forced to invest great effort recovering implicit knowledge by exploring code and interrupting teammates and this knowledge was only saved in their memory.
The relationship of organisational culture with productivity and quality
Purpose – The purpose of this paper is to explore the impact of organisational culture on productivity and quality in software organisations, with special reference to…
...
1
2
3
4
...