Collaboration in the Absence of Communication

Lars Bendix, Christian Pendleton

Research output: Chapter in Book/Report/Conference proceedingPaper in conference proceedingpeer-review

Abstract

On a software development project many people collaborate to build a product contributing different pieces of the final product. Often people on a development team will work in parallel, either on different parts or on the same parts of the product, and follow processes to co-ordinate their work with other people on the team. When teams are distributed this co-ordination becomes more difficult since there are obstacles to direct and immediate communication caused by the distribution of people in distance or time. This often gives rise to changes and contributions that are conflicting or do not work properly right away. In this case study, we investigate problems in different co-ordination processes and analyse how little and what type of communication is needed for good coordination in different situations. We suggest configuration management tool supported processes that can make it easier to co-ordinate contributions in the absence of easy communication.
Original languageEnglish
Title of host publication2014 IEEE 23rd International Wetice Conference (WETICE)
PublisherIEEE - Institute of Electrical and Electronics Engineers Inc.
Pages294-299
DOIs
Publication statusPublished - 2014
Event23rd IEEE International Conference on Enabling Technologies, Infrastructure for Collaborative Enterprises (WETICE) - Parma, ITALY
Duration: 2014 Jun 232014 Jun 25

Conference

Conference23rd IEEE International Conference on Enabling Technologies, Infrastructure for Collaborative Enterprises (WETICE)
Period2014/06/232014/06/25

Subject classification (UKÄ)

  • Computer Science

Keywords

  • collaboration
  • communication
  • workflow
  • agile
  • distributed development
  • configuration management
  • processes and tools

Fingerprint

Dive into the research topics of 'Collaboration in the Absence of Communication'. Together they form a unique fingerprint.

Cite this