Group awareness in distributed software development

By Carl Gutwin, Reagan Penner, Kevin A. Schneider. Conference on Computer Supported Cooperative Work, 2004

456 citations recorded by the source corpus.

Subfields: Computer Science Applications, Information Systems

View Paper: https://www.semanticscholar.org/paper/f80ff882f2ff8b61b9836841032e3aa0a2b895df

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Science Applications

In Information Systems

Citations in the corpus

The Mirroring Hypothesis: Theory, Evidence and Exceptions (2016, background): “(For examples, see in the across-firm case: Argyres, 1999; Andersen, 1999; Scott, 2000; Herbsleb et al., 2005; Grunwald and Kieser, 2007; in the open collaborative case: Mockus et al., 2000; Yamauchi et al., 2000; Gulley, 2001, 2004; Gutwin et al., 2004).”
Integrating Distributed Work: Comparing Task Design, Communication and Tacit Coordination Mechanisms (2011, background): “Indeed, there is some evidence based on laboratory and case studies that tacit coordination based on some form of common knowledge plays an important role in coordinating geographically distributed activity (Crampton, 2001; Gutwin et al., 2004).”
Global Software Engineering: The Future of Socio-technical Coordination (2007, background): “Gutwin et al [32] focused on understanding how open source developers use these tools to maintain both a broad awareness of the people and activities on the project as well as find specific information such as experts on a given topic.”
Social coding in GitHub: transparency and collaboration in an open software repository (2012, background): “Previous work on awareness and software development has indicated a tradeoff between specific awareness of a very small set of developer actions, versus general awareness across a project as a whole, noting the effort required to proactively provide status information (e.g. [13]).”
FASTDash: a visual dashboard for fostering awareness in software teams (2007, background): “Gutwin et al.’s [ 22 ] interviews with distributed programmers found that explicit communication methods, like email and chat, were only effective when programmers made a significant effort to stay committed to those tools.”