The small-world phenomenon: an algorithmic perspective
STOC '00 Proceedings of the thirty-second annual ACM symposium on Theory of computing
Graphs over time: densification laws, shrinking diameters and possible explanations
Proceedings of the eleventh ACM SIGKDD international conference on Knowledge discovery in data mining
Proceedings of the 2006 international workshop on Mining software repositories
The social network of Java classes
Proceedings of the 2006 ACM symposium on Applied computing
Information and Management
ASWEC '07 Proceedings of the 2007 Australian Software Engineering Conference
Communications of the ACM
Tsp(sm)-coaching development teams
Tsp(sm)-coaching development teams
Implicit Social Network Model for Predicting and Tracking the Location of Faults
COMPSAC '08 Proceedings of the 2008 32nd Annual IEEE International Computer Software and Applications Conference
Can developer-module networks predict failures?
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Proceedings of the forty-first annual ACM symposium on Theory of computing
The secret life of bugs: Going past the errors and omissions in software repositories
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Improving bug triage with bug tossing graphs
Proceedings of the the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Evolution of developer collaboration on the jazz platform: a study of a large scale agile project
Proceedings of the 4th India Software Engineering Conference
Studying team evolution during software testing
Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering
Hi-index | 0.00 |
Members of software project teams have specific roles and responsibilities which are formally defined during project inception or at the start of a life cycle activity. Often, the team structure undergoes spontaneous changes as delivery deadlines draw near and critical tasks have to be completed. Some members -- depending on their skill or seniority -- need to take on more responsibilities, while others end up being peripheral to the project's execution. We posit that this kind of ad hoc reorganization of a team's structure can be discerned from the project's bug tracker. In this paper, we extract a social network from the bug log of a real life software system and apply ideas from social network analysis to understand how the positions of individual team members in the network relate to their organizational seniority, project roles, and geographic locations that define the formal team structure. In addition to providing insights on individual team members for the system studied, our approach can serve as a framework for analyzing team dynamics of software projects.