A field study of the software design process for large systems
Communications of the ACM
The importance of ignorance in requirements engineering
Journal of Systems and Software
Requirements engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Spring algorithms and symmetry
Theoretical Computer Science - computing and combinatorics
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
Global Software Engineering: The Future of Socio-technical Coordination
FOSE '07 2007 Future of Software Engineering
Awareness in the Wild: Why Communication Breakdowns Occur
ICGSE '07 Proceedings of the International Conference on Global Software Engineering
The influence of organizational structure on software quality: an empirical case study
Proceedings of the 30th international conference on Software engineering
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
Guidelines for Effective Bridging in Global Software Engineering
ICGSE '08 Proceedings of the 2008 IEEE International Conference on Global Software Engineering
Comprehend and analyze knowledge networks to improve software evolution
Journal of Software Maintenance and Evolution: Research and Practice
Predicting build failures using social network analysis on developer communication
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
CHASE '09 Proceedings of the 2009 ICSE Workshop on Cooperative and Human Aspects on Software Engineering
Investigating Collaboration Driven by Requirements in Cross-Functional Software Teams
CIRCUS '09 Proceedings of the 2009 Collaboration and Intercultural Issues on Requirements: Communication, Understanding and Softskills
Putting it all together: using socio-technical networks to predict failures
ISSRE'09 Proceedings of the 20th IEEE international conference on software reliability engineering
Supporting enterprise stakeholders in software projects
Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering
Proceedings of the 33rd International Conference on Software Engineering
The hidden experts in software-engineering communication (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
IEEE Transactions on Software Engineering
RE '11 Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference
The impact of communication structure on new product development outcomes
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Hi-index | 0.00 |
Software projects involve diverse roles and artifacts that have dependencies to requirements. Project team members in different roles need to coordinate but their coordination is affected by the availability of domain knowledge, which is distributed among different project members, and organizational structures that control cross-functional communication. Our study examines how information flowed between different roles in two software projects that had contrasting distributions of domain knowledge and different communication structures. Using observations, interviews, and surveys, we examined how diverse roles working on requirements and their related artifacts coordinated along task dependencies. We found that communication only partially matched task dependencies and that team members that are boundary spanners have extensive domain knowledge and hold key positions in the control structure. These findings have implications on how organizational structures interfere with task assignments and influence communication in the project, suggesting how practitioners can adjust team configuration and communication structures.