Coordination in software development

By Chintan Amrit. ACM SIGSOFT Softw. Eng. Notes, 2005

501 citations recorded by the source corpus.

Subfields: Computer Science Applications, Information Systems

View Paper: https://www.semanticscholar.org/paper/9c97cb35ceb29c41628da7958ea83a439a0f5ba3

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

Expertise Integration and Creativity in Information Systems Development (2005, background): “For example, information that software architects and programmers need in the ISD process is often not available to them through documents, although analysts and end users may have this knowledge [38].”
Collaborating on Multiparty Information Systems Development Projects: A Collective Reflection-in-Action View (2005, background): “Resolving these questions is important given that coordination of diverse expertise is a critical factor in predicting project outcomes (Faraj and Sproull 2000, Kraut and Streeter 1995).”
Familiarity, Complexity, and Team Performance in Geographically Distributed Software Development (2007, background): “…beneficial for colocated software teams, it is not as critical because members who are not familiar with each other can always see and talk to each other to coordinate and exchange information about their work (Kraut and Streeter 1995, Perry et al. 1994), making team familiarity less important.”
The impact of agile practices on communication in software development (2008, background): “…different people working on a common project agree to a common definition of what they are building, share information and mesh their activities (Kraut and Streeter 1995) Goles and Chin (2005) have presented their conclusion in several research papers related to communication and argue that…”
Offshoring and the global distribution of work: Implications for task interdependence theory and practice (2009, background): “However, abstract, knowledgebased interactions and outcomes, that is, software development or R&D (Faraj & Sproull, 2000), are not so easily observable by workers and their managers (Bechky, 2003; Kiesler, Wholey, & Carley, 1994; Kraut & Streeter, 1995).”
Agile requirements engineering practices and challenges: an empirical study (2007, background): “…et al ., 2001; DeMarco & Lister, 2003; Walz et al ., 1993; Barki et al ., 1993) Customer access and participation Inadequate user–developer interaction (Curtis et al ., 1988; Keil et al ., 1998; Kraut & Streeter, 1995; Lawrence et al ., 2001) Face-to-face communication over written speciﬁcations”
An Empirical Study of Speed and Communication in Globally Distributed Software Development (2003, background): “In organizations with rapidly changing environments and " unstable " projects, informal communication is particularly important [16], [28].”
How virtual are we? Measuring virtuality and understanding its impact in a global organization (2005, background): “ICT enables interactions among workers who are not physically collocated thereby broadening their access to relevant knowledge (Cummings, 2004; Kraut & Streeter, 1995 ).”
Team Knowledge and Coordination in Geographically Distributed Software Development (2007, background): “Complex tasks with tightly coupled dependencies such as collaborative software development can beneﬁ t from coordination [21, 47].”
Virtual teams: team control structure, work processes, and team effectiveness (2004, background): “A high level of coordination among team members is also a mark of effective product development teams (Ancona and Caldwell, 1992; Kraut and Streeter, 1995; Pinto et al., 1993).”
Is the most effective team leadership shared? The impact of shared leadership, age diversity, and coordination on team performance. (2010, background): “However, all forms of team coordination typically exert positive effects on team performance (Ancona & Caldwell, 1992; Kraut & Streeter, 1995; Lewis, 2003; Nidumolu, 1995).”
A teamwork model for understanding an agile team: A case study of a Scrum project (2010, background): “Further, the model covers important elements that are found in software teams, such as coordination of work [25].”
Group awareness in distributed software development (2004, background): “, [16]) suggests that group awareness should be necessary for collaborative software development.”
Social ties, knowledge sharing and successful collaboration in globally distributed system development projects (2005, background): “Finally, the implications for theory and practice are discussed.”
Team Member Change, Flux in Coordination, and Performance: Effects of Strategic Core Roles, Information Transfer, and Cognitive Ability (2012, background): “…example, because a high level of coordination among team members is a significant indicator of effective production (e.g., Ancona & Caldwell, 1992; Kraut & Streeter, 1995; Pinto, Pinto, & Prescott, 1993), breakdowns in coordination are seen as a major obstacle inhibiting teams from realizing…”
No Workflow Can Ever Be Enough (2017, background): “Given that complex work increasingly operates under these circumstances [13], organizational behavior researchers have emphasized the need to support both formal and informal (e.g., emergent) coordination [3, 23, 35, 65].”