Software modeling and measurement: the Goal/Question/Metric paradigm
Software modeling and measurement: the Goal/Question/Metric paradigm
Empirical studies of software engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Predicting Fault Incidence Using Software Change History
IEEE Transactions on Software Engineering
Expertise recommender: a flexible recommendation system and architecture
CSCW '00 Proceedings of the 2000 ACM conference on Computer supported cooperative work
Expertise browser: a quantitative approach to identifying expertise
Proceedings of the 24th International Conference on Software Engineering
Leveraging Resources in Global Software Development
IEEE Software
Preliminary guidelines for empirical research in software engineering
IEEE Transactions on Software Engineering
An Empirical Study of Speed and Communication in Globally Distributed Software Development
IEEE Transactions on Software Engineering
Global software development in the freeBSD project
Proceedings of the 2006 international workshop on Global software development for the practitioner
Can distributed software development be agile?
Communications of the ACM
ICGSE '06 Proceedings of the IEEE international conference on Global Software Engineering
CSCW '06 Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work
Global Software Engineering: The Future of Socio-technical Coordination
FOSE '07 2007 Future of Software Engineering
Distributed Scrum: Agile Project Management with Outsourced Development Teams
HICSS '07 Proceedings of the 40th Annual Hawaii International Conference on System Sciences
Globally distributed software development project performance: an empirical analysis
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Systematic review: A systematic review of effect size in software engineering experiments
Information and Software Technology
Philips experiences in global distributed software development
Empirical Software Engineering
The influence of organizational structure on software quality: an empirical case study
Proceedings of the 30th international conference on Software engineering
Towards governance schemes for distributed software development projects
Proceedings of the 1st international workshop on Software development governance
Empirical Software Engineering
Can developer-module networks predict failures?
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Learning from Experience in Software Development: A Multilevel Analysis
Management Science
Does distributed development affect software quality? An empirical case study of Windows Vista
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Secure open source collaboration: an empirical study of linus' law
Proceedings of the 16th ACM conference on Computer and communications security
Validity concerns in software engineering research
Proceedings of the FSE/SDP workshop on Future of software engineering research
Ownership, experience and defects: a fine-grained study of authorship
Proceedings of the 33rd International Conference on Software Engineering
Don't touch my code!: examining the effects of ownership on software quality
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
Ecological inference in empirical software engineering
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Hi-index | 0.00 |
We offer a case study illustrating three rules for reporting research to industrial practitioners. Firstly, report relevant results; e.g. this paper explores the effects of dis- tributed development on software products. Second: recheck old results if new results call them into question. Many papers say distributed development can be harmful to software quality. Previous work by Bird et al. allayed that concern but a recent paper by Posnett et al. suggests that the Bird result was biased by the kinds of files it explored. Hence, this paper rechecks that result and finds significant differences in Microsoft products (Office 2010) between software built by distributed or collocated teams. At first glance, this recheck calls into question the widespread practice of distributed development. Our third rule is to reflect on results to avoid confusing practitioners with an arcane mathematical analysis. For example, on reflection, we found that the effect size of the differences seen in the collocated and distributed software was so small that it need not concern industrial practitioners. Our conclusion is that at least for Microsoft products, dis- tributed development is not considered harmful.