A field study of the software design process for large systems
Communications of the ACM
Coordination in software development
Communications of the ACM
Splitting the organization and integrating the code: Conway's law revisited
Proceedings of the 21st international conference on Software engineering
Two case studies of open source software development: Apache and Mozilla
ACM Transactions on Software Engineering and Methodology (TOSEM)
Proceedings of the international conference on Reliable software
"Breaking the code", moving between private and public work in collaborative software development
GROUP '03 Proceedings of the 2003 international ACM SIGGROUP conference on Supporting group work
Group awareness in distributed software development
CSCW '04 Proceedings of the 2004 ACM conference on Computer supported cooperative work
CSCW '06 Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work
An empirical study of software developers' management of dependencies and changes
Proceedings of the 30th international conference on Software engineering
Codebook: discovering and exploiting relationships in software repositories
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Keeping up with your friends: function Foo, library Bar.DLL, and work item 24
Proceedings of the 1st Workshop on Web 2.0 for Software Engineering
Social media for software engineering
Proceedings of the FSE/SDP workshop on Future of software engineering research
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
The problem of private information in large software organizations
Proceedings of the 2011 International Conference on Software and Systems Process
Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work
Interpretative case studies on agile team productivity and management
Information and Software Technology
Hi-index | 0.00 |
Large-scale software development requires coordination within and between very large engineering teams which may be located in different buildings, on different company campuses, and in different time zones. From a survey answered by 775 Microsoft software engineers, we learned how work was coordinated within and between teams and how engineers felt about their success at these tasks. The respondents revealed that the most common objects of coordination are schedules and features, not code or interfaces, and that more communication and personal contact worked better to make interactions between teams go more smoothly.