9th IEEE International Conference on Collaborative Computing: Networking, Applications and Worksharing

Research Article

When to Interrupt Global Software Engineers to Provide them with What Information?

Download275 downloads
  • @INPROCEEDINGS{10.4108/icst.collaboratecom.2013.254099,
        author={Ben van Gameren and Rini van Solingen},
        title={When to Interrupt Global Software Engineers to Provide them with What Information?},
        proceedings={9th IEEE International Conference on Collaborative Computing: Networking, Applications and Worksharing},
        publisher={ICST},
        proceedings_a={COLLABORATECOM},
        year={2013},
        month={11},
        keywords={global software engineering awareness virtual office walls information interruptions estimate-talk-estimate study},
        doi={10.4108/icst.collaboratecom.2013.254099}
    }
    
  • Ben van Gameren
    Rini van Solingen
    Year: 2013
    When to Interrupt Global Software Engineers to Provide them with What Information?
    COLLABORATECOM
    IEEE
    DOI: 10.4108/icst.collaboratecom.2013.254099
Ben van Gameren1,*, Rini van Solingen1
  • 1: Delft University of Technology
*Contact email: b.j.a.vangameren@tudelft.nl

Abstract

Software Engineering is a highly collaborative activity in which knowledge about the work context is essential to collaborate effectively. Acquiring such knowledge is difficult in a distributed setting, since developers have to manually analyze, filter and combine available information in order to acquire a sufficient level of awareness. Therefore, it seems beneficial to construct a mechanism which automatically regulates information based on both the current activity of a software engineer and the importance of the new information. In this paper we present an Estimate-Talk-Estimate study, with experienced software engineers, in which we studied both (i) what information software engineers want to know immediately and (ii) when software engineers do not mind to be interrupted with such information. The main findings include a list of information items which software engineers want to be immediately informed about, and a list of activities during which software engineers prefer not to be interrupted.