Online collaboration: Collaborative behavior patterns and factors affecting globally distributed team performance

Studying the collaborative behavior of online learning teams and how this behavior is related to communication mode and task type is a complex process. Research about small group learning suggests that a higher percentage of social interactions occur in synchronous rather than asynchronous mode, and that students spend more time in task-oriented interaction in asynchronous discussions than in synchronous mode. This study analyzed the collaborative interaction patterns of global software development learning teams composed of students from Turkey, US, and Panama. Data collected from students’ chat histories and forum discussions from three global software development projects were collected and compared. Both qualitative and quantitative analysis methods were used to determine the differences between a group’s communication patterns in asynchronous versus synchronous communication mode. K-means clustering with the Ward method was used to investigate the patterns of behaviors in distributed teams. The results show that communication patterns are related to communication mode, the nature of the task, and the experience level of the leader. The paper also includes recommendations for building effective online collaborative teams and describes future research possibilities.     

Computer-mediated communication to support distributed requirements elicitations and negotiations tasks

Requirements engineering is one of the most communication-intensive activities in software development, greatly affected by project stakeholder geographical distribution. Despite advances in collaboration technologies, global software teams continue to experience significant challenges in the elicitation and negotiation of requirements. Deciding which communication technologies to deploy to achieve effective communication in distributed requirements engineering activities is not a trivial task. Is face-to-face or text-based communication more appropriate for requirements elicitations and negotiations? In teams that do not have access to face-to-face communication, is text-based communication more useful in requirements elicitations than in requirements negotiations? Here, we report an empirical study that analyzes the effectiveness of synchronous computer-mediated communication in requirements elicitations and negotiations. Our investigation is guided by a theoretical framework that we developed from theories of computer-mediated communication, common ground, and media selection for group tasks; a framework that considers the effectiveness of a communication medium in relation to the information richness needs of requirements elicitation and negotiation tasks. Our findings bring forward empirical evidence about the perceived as well as objective fit between synchronous communication technology and requirements tasks. First, face-to-face is not always the most preferred medium for requirements tasks, and we reveal a number of conditions in which, in contrast to common belief, text-based communication is preferred for requirements communication. Second, we find that in evaluating outcomes of requirements elicitations and negotiations objectively, group performance is not affected by the communication medium. Third, when groups interact only via text-based communication, common ground in requirements negotiations takes longer to achieve than in requirements elicitations, indicating that distributed requirements elicitation is the task where computer-mediated communication tools have most opportunity for successful application.     

Reasoning on infeasibility in distributed collaborative computing environment

Collaborative computing is a new communication technology that makes it possible to extend model formulation, management, and analysis into a geographically distributed group environment. The forms of communication may vary from asynchronous hypermedia teamwork via the Internet to multipoint desktop video conferencing. The latter presents the maximal potential for integrating shared quantitative model analysis with real-time/asynchronous geographically distributed electronic meetings. Infeasibility diagnosis and reasoning on conflict resolution are known to be important parts of an evolving approach to linear programming model analysis. In the new distributed environment, several specific decision support issues related to infeasibility analysis emerge. One is the learning mechanism for capturing group knowledge on infeasibility resolution that is generated during the collaborative sessions of model analysis. The other new decision support component is a coordination protocol that is capable of linking individual activities and software transactions for the support of group reasoning on infeasibility analysis. This paper addresses these issues on the basis of committee models for infeasibility resolution and the neural network approach. Examples of modeling cases are based on experiments using a multiple criteria model for support of resource allocation in a distributed electronic meeting, and the case of model-based diagnosis that the group is involved in.     

A new architecture for a collaborative authoring system

Much research has occurred in recent years detailing computer systems which support collaborative writing. In this paper we describe a collaborative authoring system capable of handling both synchronous and asynchronous communication between authors, based upon a writing model of coordination, writing, annotation, consolidation and negotiation. This assumes that the negotiation aspects play a major role in the collaborative process. A model linking the logical structure of documents and author roles is also established, based on the Standard Generalized Markup Language.     

A comparative content analysis of face-to-face vs. asynchronous group decision making

A field experiment was conducted to analyze the process and contents of group discussions. Groups solved a case study either orally or through an asynchronous computer-mediated communication system. Findings show that asynchronous groups had broader discussions and submitted more complete reports than their face-to-face counterparts. However, there was no difference in the ability to transfer information from the discussion to the report; under both conditions, about 15% of the issues mentioned in the discussion were omitted from the final report. In terms of coordination, face-to-face teams covered the case study questions sequentially, while asynchronous groups were more focused on solving their general disagreements.     

A distributed problem-solving approach to collaborative facility engineering

A framework for collaborative facility engineering is presented. The framework is based on a distributed problem-solving approach to collaborative facility engineering and employs an integration approach called Agent-Based Software Engineering as an implementation vehicle of this approach. The focal entity of this framework is a Multiagent Design Team (MDT) that comprises a collection of software agents (e.g. design software applications with a certain standard communication interface) and a design specialist, which together perform specific design tasks. Multiagent design teams are autonomous and form an organizational structure based on a federation architecture. Every multiagent design team surrenders its autonomy to a system program called facilitator, which coordinates the interaction among software agents in the federation architecture. Facilitators can be viewed as representatives of one or more teams that facilitate the exchange of design information and knowledge in support of the design tasks they perform. In the federation architecture, design specialists collaborate by exchanging design information with others via their software agents, and by identifying and resolving design conflicts by negotiation. In addition to a discussion of the framework's primary components, its realization in an integrated distributed environment for collaborative building engineering is described.     

A conceptual model for negotiating in service-oriented environments

In recent years, Web services have been developed as a fundamental technique for the new generation of B2B or EAI applications. As they have matured and a new vision of service-oriented computing has emerged, the software industry has shifted its attention from developing required software to delivering desired services. In order to benefit from such a service-oriented model of software, several critical issues must be addressed in a service-oriented environment such as differentiation of services by various attributes, dynamic selection and provision of services in a supply chain style, and commitment of services with prescribed rules. From the managerial perspective, these issues are concerned with a process of negotiating desired services in a service-oriented environment. In this paper, we propose an object-oriented model that specifies such a negotiation process by architectural constructs where these critical issues are adequately addressed. The model contains a use case diagram that depicts requirements for the negotiation process, an architecture diagram that describes collaborative components for satisfying these requirements, and a class/sequence diagram that specifies class objects in these components to perform all behaviors occurring within the negotiation process. For illustration, the model is applied to an exemplified negotiation process for book publishing.     

A Study of Users’ Reactions to a Mixed Online Discussion Model: A Lag Sequential Analysis Approach

There is an increasing growth of Social Network Services (SNSs). A variety of SNSs are applied in online interpersonal platforms. Among them, asynchronous and synchronous discussions are widely examined. However, there is a lack of research into the effects of integrated discussion services that combines asynchronous and synchronous discussions. Thus, the study investigates users’ performances and behavior patterns in a mixed discussion model that integrates asynchronous and synchronous discussions with a lag sequential analysis. The results showed that most groups chose to adopt the mixed discussion model (i.e., using both synchronous and asynchronous discussions), and only one group totally adopted the asynchronous discussion model. The study further analyzed the learners’ learning effectiveness and behavioral patterns, and the results indicated that the groups using the mixed model had a positive performance to a certain extent in terms of learning effectiveness and knowledge construction. In addition, users with the mixed discussion model demonstrated diverse behaviors, which were more complex than that of those with a single-way discussion model. Furthermore, regarding the groups using “balanced synchronous and asynchronous discussions” and the groups “mainly using synchronous discussion supplemented by less asynchronous discussion” in the mixed model (simultaneously using synchronous and asynchronous discussions), those users who mainly used synchronous discussion supplemented by asynchronous discussion had more diverse behaviors of knowledge construction.     

Decentralized control of distributed intelligent robots and subsystems

In a distributed robot system, asynchronous and synchronous communication between the system components is necessary to guarantee problem soliving capability in realtime. On that account, the distributed control architecure of the Karlsruhe Autonomous Mobile Robot KAMRO which is being developed at IPR has been extended by these communication kinds. The robot system consists of several subcomponents, like manipulators, two hand-eyecameras, one overhead camera and a mobile platform. To get better problem solving capability than the former centralized control architecture, these components are able to work together in teams (asynchronous communication) or special agents (synchronous communication).     

A tool supporting root cause analysis for synchronous retrospectives in distributed software teams

ContextRoot cause analysis (RCA) is a useful practice for software project retrospectives, and is typically carried out in synchronous collocated face-to-face meetings. Conducting RCA with distributed teams is challenging, as face-to-face meetings are infeasible. Lack of adequate real-time tool support exacerbates this problem. Furthermore, there are no empirical studies on using RCA in synchronous retrospectives of geographically distributed teams.ObjectiveThis paper presents a real-time cloud-based software tool (ARCA-tool) we developed to support RCA in distributed teams and its initial empirical evaluation. The feasibility of using RCA with distributed teams is also evaluated.MethodWe compared our tool with 35 existing RCA software tools. We conducted field studies of four distributed agile software teams at two international software product companies. The teams conducted RCA collaboratively in synchronous retrospective meetings by using the tool we developed. We collected the data using observations, interviews and questionnaires.ResultsComparison revealed that none of the existing 35 tools matched all the features of our ARCA-tool. The team members found ARCA-tool to be an essential part of their distributed retrospectives. They considered the software as efficient and very easy to learn and use. Additionally, the team members perceived RCA to be a vital part of the retrospectives. In contrast to the prior retrospective practices of the teams, the introduced RCA method was evaluated as efficient and easy to use.ConclusionRCA is a useful practice in synchronous distributed retrospectives. However, it requires software tool support for enabling real-time view and co-creation of a cause-effect diagram. ARCA-tool supports synchronous RCA, and includes support for logging problems and causes, problem prioritization, cause-effect diagramming, and logging of process improvement proposals. It enables conducting RCA in distributed retrospectives.     

Enhancing collaborative synchronous UML modelling with fine-grained versioning of software artefacts

Software development teams are composed of people with different knowledge and skills, who contribute to a project from often widely dispersed locations. Software development in geographically distributed environments creates software engineering challenges due to the interaction among members of distributed teams and the management of consistency and concurrency among project artefacts. In this paper, we propose Synchronous collaborative modelling Tool Enhanced with VErsioning management (STEVE) a collaborative tool supporting distributed Unified Modelling Language (UML) modelling of software systems. The tool provides a communication infrastructure enabling the concurrent editing of the same UML diagram at the same time by distributed developers. Complex UML diagrams are decomposed and managed in a fine-grained hierarchy of sub-artefacts, thus providing change and configuration management functionalities for both the diagram and the graphical objects. Thus, software predefined diagram components can be consistently reused and shared across different diagrams of a given project.     

Test-Driven Development in Large Projects

Test-driven development (TDD) is a key practice for agile developers because it involves writing test cases ahead of the code, which can improve design. The TDD process works well for projects in which a collocated team develops a small to medium system, but it can be challenging for large systems, especially those involving geographically distributed teams. The main obstacle is the degree of integration: when the team must integrate many individual classes developed at distributed sites, the coordination and communication grows exponentially with the number of individual developers and sites. This does not mean that TDD is ineffective for large-scale geographically distributed projects, but developers must take care to account for its focus on unit testing and its failure to rigorously address communications issues during system and integration testing. In this article, suggestions to scale up TDD are presented with two large-scale global software development projects at a major corporation and a recent meeting to exchange global software development best practices with a Fortune 500 company     

Managing Problems for Global Software Production – Experience and Lessons

With the increase in size and complexity of current software projects, many large companies have established global software production lines over the world to develop and deliver software products with collaborative software development processes involving multiple teams located at different sites. Supporting global software production needs an effective software-engineering environment to meet the special requirements of the collaborative software development process, diverse management methods and engineering practice. WWW technology provides powerful means to set up an enterprise-oriented software engineering environment for global software production due to its advantages in networking, global access, internationalization, and communication. Although there are many articles addressing the methods and experience in building web-based applications systems and tools, very few papers discuss the real-world problems and solutions in the development and deployment of web-based software tools to support a collaborative software development process for global software production. This paper discusses the real world issues, and reports our experience and lessons in building and deploying a web-based problem information management system (PIMS) to support global software development processes at Fujitsu. It focuses on the real issues and needs of current collaborative development process involving multiple teams, and highlights the benefits and impact of the PIMS on global software production. Moreover, it discusses our technical solutions and trade-offs in the development of PIMS, and shares our experience and lessons. Furthermore, it introduces a new data-centered conceptual process model to support diverse collaborative processes for project and problem management in global software production. Finally, the paper shares our key successes and weaknesses, and reports our experience and lessons in the deployment of the system.     

Leveraging distributed software development

The Internet has been changing the way people collaborate on software development, offering certain advantages but also creating new requirements. Internet based collaboration does make a wider base of talent available, but the development cycles running at Internet speeds require maintaining higher levels of precision. From a project management perspective, communication is a key factor in Internet based development. Internet based collaboration requires effective team communication. The authors point out that when a development team isn't communicating well, it is nearly impossible to create and validate design solutions and manage the team's deliverables. So while Internet collaboration offers a number of advantages, the friction created by distributed (therefore delayed) communication typically increases the overhead associated with sharing project information. And the technology itself, including system interoperability and the synchronous or asynchronous collaboration tools, can create problems in a distributed development environment. As the complexities of distributed collaborative development environments increase, frameworks designed for such environments will become essential. The authors describe one such framework called SoftDock, and the new technologies it exploits. It lets developers analyze, design, and develop software from component models     

Social ties,knowledge sharing and successful collaboration in globally distributed system development projects

Traditionally, the main focus of the information system (IS) literature has been on technical aspects related to system development projects. Furthermore, research in the IS field has mainly focused on co-located project teams. In this respect, social aspects involved in IS projects were neglected or scarcely reported. To fill this gap, this paper studies the contribution of social ties and knowledge sharing to successful collaboration in distributed IS development teams. Data were drawn from two successful globally distributed system development projects at SAP and LeCroy. Data collected were codified using Atlas.ti software. The results suggest that human-related issues, such as rapport and transactive memory, were important for collaborative work in the teams studied. The paper concludes by discussing the implications for theory and suggesting a practical guide to enhance collaborative work in globally distributed teams.     

A decentralized architecture for software process modeling andenactment

Many development teams, especially distributed teams, require process support to adequately coordinate their complex, distributed work practices. Process modeling and enactment tools have been developed to meet this requirement. The authors discuss the Serendipity-II process management environment which supports distributed process modeling and enactment for distributed software development projects. Serendipity-II is based on a decentralized architecture and uses Internet communication facilities     

The potential of synchronous communication to enhance participation in online discussions: A case study of two e-learning courses

Computer-mediated communication (CMC) has been adopted in most e-learning settings. However, few research studies have considered the effect of different CMC. This study examined how and why synchronous communication affected participation in online discussions. Two online classes that participated in two asynchronous and two synchronous online discussions were examined. Actual and perceived measures of participation indicated that synchronous communication induced personal participation, which could be regarded as a complement to cognitive participation. Personal participation involves more intense interaction better supported by synchronous communication while cognitive participation is a more reflective type of participation supported by asynchronous communication. In synchronous discussions, the e-learners felt that they worked together and were not restricted to only discuss course content. This was likely to induce arousal and motivation and increased convergence on meaning, especially in small groups.     

How to get mature global virtual teams: a framework to improve team process management in distributed software teams

Managing global software development teams is not an easy task because of the additional problems and complexities that have to be taken into account. This paper defines VTManager, a methodology that provides a set of efficient practices for global virtual team management in software development projects. These practices integrate software development techniques in global environments with others such as explicit practices for global virtual team management, definition of skills and abilities needed to work in these teams, availability of collaborative work environments and shared knowledge management practices. The results obtained and the lessons learned from implementing VTManager in a pilot project to develop software tools for collaborative work in rural environments are also presented. This project was carried out by geographically distributed teams involving people from seven countries with a high level of virtualness.     

Distributed Java applets for project management on the Web

The rapid evolution of our data communications infrastructure is making distributed projects increasingly viable. Without a common infrastructure, computer-supported collaborative tools for distributed teams have been prohibitively expensive to build and maintain. However, the increasing availability of the Internet is enabling companies to develop cost-effective collaborative solutions. Traditional desktop project management software is designed as a single-user tool that lets the project manager track tasks, milestones and deliverables. As teams spread over geographic distances with multiple centers of control, the communication, coordination, and tracking of ongoing project activity become key issues for project success. This article looks beyond the traditional planning focus of project management applications to a network-centric focus on collaboration. It describes the implementation of ActionPlan, a 100 percent Java-based application from Netmosphere that supports real-time collaboration among Java thin clients to facilitate distributed project management     

Predictive resource management for meta-applications

This paper defines meta-applications as large, related collections of computational tasks, designed to achieve a specific overall result, running on a (possibly geographically) distributed, non-dedicated meta-computing platform. To carry out such applications in an industrial context, one requires resource management and job scheduling facilities (including capacity planning), to ensure that the application is feasible using the available resources, that each component job will be sent to an appropriate resource, and that everything will finish before the computing resources are needed for other purposes.

This requirement has been addressed by the PAC in three major European collaborative projects: PROMENVIR, TOOLSHED and HPC-VAO, leading to the creation of job scheduling software, in which scheduling is brought together with performance modelling of applications and systems, to provide meta-applications management facilities. This software is described, focusing on the performance modelling approach which was needed to support it.

Early results from this approach are discussed, raising some new issues in performance modelling and software deployment for meta-applications. An indication is given about ongoing work at the PAC designed to overcome current limitations and address these outstanding issues.