Proceedings of the 2006 international workshop on Mining software repositories
ASWEC '07 Proceedings of the 2007 Australian Software Engineering Conference
The influence of organizational structure on software quality: an empirical case study
Proceedings of the 30th international conference on Software engineering
Can developer-module networks predict failures?
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Does distributed development affect software quality?: an empirical case study of Windows Vista
Communications of the ACM - A Blind Person's Interaction with Technology
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
A social network based study of software team dynamics
Proceedings of the 3rd India software engineering conference
| Hi-index | 0.00 |
Software development teams are one of the most dynamic entities of any software development project. While the individuals are assigned planned roles at the start of any project, during the course of the project, the team constitution, structure, relationships and roles change. Such changes are often spontaneous and constitute the evolution of the team along different phases of the software development lifecycle. As software development is a team effort, these dynamics may have a significant effect on the development lifecycle itself. This work is aimed at studying the evolution of project teams and gathering insights that can be correlated with project health and outcomes. In this study we apply social network analysis techniques to investigate team evolution in a project in its testing phase. While the questions and insights that we investigate in this paper are valid and useful for all phases of the software development lifecycle, we have focused on software testing phase as it one of the most critical phases in the lifecycle. Our work aims to provide insights in the changes in team interactions and individual roles as the testing process continues and can help find if the same is aligned to the planned and desired project behavior.