Exploring collaboration patterns among global software development teams.

This study examines communication behaviors in global software student teams. The authors of the paper characterize the types of communication behaviors that occur when student teams are engaged in a software development project. The authors present findings from a one-semester study that examined factors contributing to successful distributed programming interactions among students enrolled at the University of Atilim (Turkey), Universidad Tecnológica de Panamá, University of North Texas, and Middlesex University (UK). Using content and cluster analyses techniques, we identified distinct patterns of collaboration and examined how these patterns were associated with task, culture, GPA, and performance of collaborative teams. Our results suggest that communication patterns among global software learners may be related to task type, culture and GPA. It is hoped that these findings will lead to the development of new strategies for improving communication among global software teams

Sustainable Software Ecosystems: Software Engineers, Domain Scientists, and Engineers Collaborating for Science

The development of scientific software is often a partnership between domain scientists and scientific software engineers. It is especially important to embrace these collaborations when developing advanced scientific software, where sustainability, reproducibility, and extensibility are important. In the ideal case, as discussed in this manuscript, this brings together teams composed of the world's foremost scientific experts in a given field with seasoned software developers experienced in forming highly collaborative teams working on software to further scientific research.Comment: 4 pages, submission for WSSSPE

Team-oriented process programming

Team-oriented process programming promises to provide significant support for the planning, directing, and controlling of software engineering projects. In this paper we apply process programming to software engineering teams and show how this can provide powerful new capabilities for the management of software projects. We identify key issues which must be addressed to apply process programming to teams, and present our vision for team-oriented process programming

The mystery of the writing that isn’t on the wall: differences in public representations in traditional and agile software development

This paper considers the use of public displays, such as whiteboards and papers pinned to walls, by different software development teams, based on evidence from a number of empirical studies. This paper outlines differences in use observed between traditional and agile teams and begins to identify the implications that they may have for software development

The Importance of Conflict Resolution Techniques in Autonomous Agile Teams

Today, software companies usually organize their work in teams. Social science research on team development has shown that for a team to reach a productive and autonomous stage, it has to be able to manage internal conflicts and disagreements efficiently. To better facilitate the team development process, we argue that software engineers' needs additional training in negotiation skills and conflict resolution. In this position paper, we outline ideas for what aspects to consider in such training. As an example, we argue that a majority of the conflicts originate from team-level factors and that they, therefore, should be managed on the team-level instead of in relation to dyads.Comment: Accepted at 1st International Workshop on Autonomous Teams (A-TEAMS), 201