Coordination in software development
Communications of the ACM
The mythical man-month (anniversary ed.)
The mythical man-month (anniversary ed.)
The Mutual Knowledge Problem and Its Consequences for Dispersed Collaboration
Organization Science
An Empirical Study of Speed and Communication in Globally Distributed Software Development
IEEE Transactions on Software Engineering
Exploratory Social Network Analysis with Pajek
Exploratory Social Network Analysis with Pajek
Building Defect Prediction Models in Practice
IEEE Software
Leveraging expertise in global software teams: Going outside boundaries
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
CSCW '06 Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work
Using Multivariate Statistics (5th Edition)
Using Multivariate Statistics (5th Edition)
ICGSE '07 Proceedings of the International Conference on Global Software Engineering
Jazz and the Eclipse Way of Collaboration
IEEE Software
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
Latent social structure in open source projects
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Communication networks in geographically distributed software development
Proceedings of the 2008 ACM conference on Computer supported cooperative work
Software Process: Improvement and Practice - Global Software Development: Where Are We Headed?
Learning from Experience in Software Development: A Multilevel Analysis
Management Science
Predicting build failures using social network analysis on developer communication
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Mining the Jazz repository: Challenges and opportunities
MSR '09 Proceedings of the 2009 6th IEEE International Working Conference on Mining Software Repositories
Quantitative Modeling of Communication Cost for Global Service Delivery
SCC '09 Proceedings of the 2009 IEEE International Conference on Services Computing
Predicting defects with program dependencies
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
Putting it all together: using socio-technical networks to predict failures
ISSRE'09 Proceedings of the 20th IEEE international conference on software reliability engineering
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
IEEE Transactions on Software Engineering
Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work
Bug resolution catalysts: identifying essential non-committers from bug repositories
Proceedings of the 10th Working Conference on Mining Software Repositories
Hi-index | 0.00 |
IBM's Jazz initiative offers a state-of-the-art collaborative development environment (CDE) facilitating developer interactions around interdependent units of work. In this paper, we analyze development data across two versions of a major IBM product developed on the Jazz platform, covering in total 19 months of development activity, including 17,000+ work items and 61,000+ comments made by more than 190 developers in 35 locations. By examining the relation between developer talk and work, we find evidence that developers maintain a reasonably high level of connectivity with peer developers with whom they share work dependencies, but the span of a developer's communication goes much beyond the known dependencies of his/her work items. Using multiple linear regression models, we find that the number of defects owned by a developer is impacted by the number of other developers (s)he is connected through talk, his/her interpersonal influence in the network of work dependencies, the number of work items (s)he comments on, and the number work items (s)he owns. These effects are maintained even after controlling for workload, role, work dependency, and connection related factors. We discuss the implications of our results for collaborative software development and project governance.