Effects of intra‐group conflict on packaged software development team performance

Sawyer, Steve

doi:10.1046/j.1365-2575.2001.00100.x

Cited by 79 publications

(85 citation statements)

References 56 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Conflicts arise in both FOSSD [18,33] and traditional software development projects [56], and finding ways to resolve conflicts becomes part of the cost (in terms of social capital) that must be incurred by FOSS developers for development progress to occur. Minimizing the occurrence, duration, and invested effort in such conflicts quickly becomes a goal for the core developers in an FOSSD project.…”

Section: Cooperation Coordination and Control In Foss Projectsmentioning

confidence: 99%

Collaboration Practices and Affordances in Free/Open Source Software Development

Scacchi

2010

Collaborative Software Engineering

View full text Add to dashboard Cite

Abstract. This chapter examines collaborative work practices, development processes, project and community dynamics, and other socio-technical relationships in free and open source software development (FOSSD). It also describes what kinds of collaboration affordances facilitate collaborative work in FOSSD projects. It reviews a set of empirical studies of FOSSD that articulate different levels of analysis. Finally, there is discussion of limitations and constraints in understanding what collaboration practices and affordances arise in FOSSD studies and how they work, and then to emerging opportunities for future FOSSD studies.

show abstract

Section: Cooperation Coordination and Control In Foss Projectsmentioning

confidence: 99%

Collaboration Practices and Affordances in Free/Open Source Software Development

Scacchi

2010

Collaborative Software Engineering

View full text Add to dashboard Cite

show abstract

“…We use the measurement of Berman and West [17] to test the level of the IS developers' emotional intelligence, from the aspect of relationship management. The factor of conflict control is measured by the items adapted from Sawyer [18], while the communication quality is tested by adapting the items from Han, et al [19]. And the factors of characteristic of the developer and characteristic of the project are both measured by the items adapted from Guinan, et al [20].…”

Section: A Instrument Developmentmentioning

confidence: 99%

How to Increase the Quality of Requirements Analysis in Information System Development - The View from Emotional Intelligence

Xiang¹

2016

Proceedings of the 3d International Conference on Applied Social Science Research

View full text Add to dashboard Cite

-Accurate requirements are essential to the success of any information system development project. Over the years, numerous studies have investigated factors such as attitude, behavior, and performance that affect the information systems development (ISD) process. Our research focused on how developers' behavior affected end users and the requirements analysis from the emotional intelligence perspective. Specifically, we examined emotional intelligence factors (the quality of communication, control of conflicts between developers and users, and the developers' attitude towards the users) and enterprise characteristics (characteristics of developers, the stability of the staff in the development enterprise, and the characteristics of the project). Using data collected from ISD firms in China, we show that emotional intelligence and enterprise characteristics can both have positive effects on requirements analysis.

show abstract

“…The researchers who carried out the previous SE studies (Elam & Walz, 1988;Gobeli, Koenig, & Bechinger, 1998;P. Sawyer et al, 1999;S. Sawyer, 2001) concluded that SE environments should not be conflict free; rather, they should be conflict managed.…”

Section: Team Cmentioning

confidence: 99%

Measuring the effect of conflict on software engineering teams

Karn

Cowling

2008

Behavior Research Methods

View full text Add to dashboard Cite

582This article describes how observational methods were used to ascertain the effect of conflict on the performance of software engineering (SE) teams during the important feasibility, requirements analysis, and design phases of software projects, and the subsequent development of social and conflict interaction protocols to allow researchers to record conflict episodes when they occurred. Three teams consisting of master of science (MSc) students at the University of Sheffield were observed as they worked through the feasibility, analysis, and design phases of the SE life cycle. Each occurrence of conflict between team members was recorded, as well as the form and intensity of the conflict.There were several reasons for pursuing this line of research. The first is that commercial SE is a team-based activity, and, as in other related contexts, success is dependent to a large extent on whether or not team members have succeeded in establishing a cooperative environment (Cohen & Bailey, 1997). Additionally, several scholars have opined that the social factors of SE are potentially more important than the technical aspects (Curtis, 1991(Curtis, , 1998Curtis, Krasner, & Iscoe, 1988;Curtis, Walz, & Elam, 1993). This view is reinforced by other scholars who hold the belief that future SE research should focus more on human factors (Crowston & Kammerer, 1998a, 1998bPetre, Budgen, & Scholtz, 2004). The rationale behind this argument is that further exploration into these areas will play an important role in the maturation of SE as an academic discipline.The importance of teamwork in SE has long been recognized at a pedagogic level. It is now common for SE degree programs to include one or more team projects. These projects should enable team members to develop what has been termed positive interdependence (Johnson & Johnson, 1978), which theoretically should result in enhanced short-term memory, long-term retention, greater understanding of course material, and critical thinking and problem-solving skills.Although there are numerous advantages to working in teams, there are also several problems that one needs to be aware of (Harris & Looney, 1999). Harris and Looney stated that one of the main problems is that a team approach to a project usually generates a greater degree of conflict than many people are accustomed to. This conflict can be a serious impediment to performance.This situation raises the question of what the exact nature of conflict actually is. Some (Amason, 1996;Galinsky, 2002;Jehn, 1995) have argued that conflict is an inevitable and pervasive aspect of organizational life. People are said to be in conflict when the actions of one person are interfering, obstructing, or in some other way making another's behavior less effective (Tjosvold, 1997).Previous team-process research has distinguished three separate forms of conflict: task (or cognitive), relationship (or affective) (Amason, 1996;Amason & Schweiger, 1994;Pinkley, 1990), and process (Jehn, 1995). These forms of conflict have been found to have ...

show abstract

Effects of intra‐group conflict on packaged software development team performance

Cited by 79 publications

References 56 publications

Collaboration Practices and Affordances in Free/Open Source Software Development

Collaboration Practices and Affordances in Free/Open Source Software Development

How to Increase the Quality of Requirements Analysis in Information System Development - The View from Emotional Intelligence

Measuring the effect of conflict on software engineering teams

Contact Info

Product

Resources

About