Increasing awareness in distributed software teams: A first evaluation

Similarly to co-located software engineering teams, teams in which developers work geographically distributed require a variety of information about the project, organization and team members to collaborate effectively. However, in such a setting, maintaining awareness at a sufficient level to collaborate optimally is generally more difficult. Therefore research has been done on the prioritization of information for distributed software engineers, based on their current activity and status. Based on this research a platform was developed incorporating a subset of the findings. In this paper we report on a first evaluation of the deployment of this platform in a distributed industrial case setting. The most important findings are that: (i) providing distributed software engineers with their information needs, appears to contribute to an increase in their overall level of awareness and (ii) information about project related communication with the customer and information about the happiness of colleagues adds the most value.

[1]  Rini van Solingen,et al.  Auto-erecting virtual office walls , 2012, 8th International Conference on Collaborative Computing: Networking, Applications and Worksharing (CollaborateCom).

[2]  SharpHelen,et al.  Cooperative and human aspects of software engineering , 2013 .

[3]  Philippe A. Palanque,et al.  Proceedings of the SIGCHI Conference on Human Factors in Computing Systems , 2014, International Conference on Human Factors in Computing Systems.

[4]  Grady Booch,et al.  Collaborative Development Environments , 2003, Adv. Comput..

[5]  Daune West,et al.  The Appreciative Inquiry Method , 1991 .

[6]  Robert J. Walker,et al.  Promoting developer-specific awareness , 2008, CHASE '08.

[7]  Li-Te Cheng,et al.  Shared waypoints and social tagging to support collaboration in software development , 2006, CSCW '06.

[8]  Mary Czerwinski,et al.  FASTDash: a visual dashboard for fostering awareness in software teams , 2007, CHI.

[9]  Erran Carmel,et al.  Global software teams: collaborating across borders and time zones , 1999 .

[10]  J. H. Frey,et al.  The Interview: From Neutral Stance to Political Involvement. , 2005 .

[11]  Bertrand Meyer,et al.  News and Notification : Propagating Relevant Changes to Developers Software , 2012 .

[12]  Kevin Dullemond,et al.  An Industrial Evaluation of Technological Support for Overhearing Conversations in Global Software Engineering , 2011, 2012 IEEE Seventh International Conference on Global Software Engineering.

[13]  Audris Mockus,et al.  Expertise Browser: a quantitative approach to identifying expertise , 2002, Proceedings of the 24th International Conference on Software Engineering. ICSE 2002.

[14]  Arie van Deursen,et al.  Fixing the ‘Out of sight out of mind’ problem one year of mood-based microblogging in a distributed software team , 2013, 2013 10th Working Conference on Mining Software Repositories (MSR).

[15]  Randall Frost,et al.  Jazz and the Eclipse Way of Collaboration , 2007, IEEE Software.

[16]  John C. Tang.  Findings from Observational Studies of Collaborative Work , 1991, Int. J. Man Mach. Stud..

[17]  Rini van Solingen,et al.  Collaboration should become a first-class citizen in support environments for software engineers , 2012, 8th International Conference on Collaborative Computing: Networking, Applications and Worksharing (CollaborateCom).

[18]  Paul Dourish,et al.  Awareness and coordination in shared workspaces , 1992, CSCW '92.

[19]  Vijay K. Vemuri,et al.  Global Software Teams: Collaborating Across Borders and Time Zones , 2002 .

[20]  Kevin Dullemond,et al.  What Distributed Software Teams Need to Know and When: An Empirical Study , 2013, 2013 IEEE 8th International Conference on Global Software Engineering.

[21]  Stephanie D. Teasley,et al.  Learning by tagging: group knowledge formation in a self-organizing learning community , 2006 .