CoChat

Managing Conflict in Software Development Teams: A Multilevel Analysis

Open access
David H. Gobeli, Harold F. Koenig, Iris Bechinger · 1998 · Journal of Product Innovation Management
Cited by 100

The DOI matches its OpenAlex record; 2 of the 2 references it cites were found in a registry or an index.

Abstract

For a new product development (NPD) organization, a little conflict can be a good thing. Healthy disagreements can push project team members or different functional groups in an organization to pursue more in-depth, insightful analysis. This type of creative tension can help to engender an environment that encourages innovation and thus keeps NPD efforts free from the business-as-usual doldrums. However, management must ensure that conflict remains on a healthy level. David H. Gobeli, Harold F. Koenig, and Iris Bechinger note that conflict must be managed not only to increase the satisfaction of project team members, but also to achieve strategic project success. To provide better understanding of the important issues in conflict management, they examine the effects of three conflict factors on software development project success: context, conflict intensity, and conflict management style. Using survey responses from 117 software professionals and managers, they develop a multi-level framework of success versus conflict for team-based, software development projects. Within this framework, they examine context, conflict intensity, and conflict management approaches at the team and organization levels. For the participants in this study, unresolved conflict has a strong, negative effect on overall software product success and customer satisfaction. Project team member satisfaction decreases substantially with higher intensity conflict at the organization level, and even more strongly at the project level. For the respondents to this study, the combined effects of conflict intensity and conflict management style on project success are significant, but they are not as great as the combined effects of such context variables as company goals, group dynamics, and management support. Two conflict management styles—confronting and give and take—have beneficial effects on success at the organization level for the firms in this study. Smoothing, withdrawal, and forcing all have negative effects, although only forcing has a statistically significant negative effect. In general terms, the results suggest that management should guard against frequent use of the dysfunctional management styles—withdrawal, smoothing, and forcing. The results suggest that emphasis on confrontation—that is, true problem solving—is essential at the project level, even if a give-and-take style is better tolerated at the organization level.

Overview

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

OpenAlex · 10.1016/s0737-6782(98)00011-3

Cites

2 of 2 references verified0 citation errors · 0 not checkable

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cites

Show all 2 references

Cited by

See all 100

Metadata

Authors
Gobeli, D. H., Koenig, H. F., & Bechinger, I.
Venue
Journal of Product Innovation Management
Publisher
Wiley
Published
1998-09-01
Volume
15
Issue
5
Pages
423-435
ISSN
0737-6782 (ISSN-L)
OpenAlex
W1990586784
Cited by
100
References
2
FWCI
5.74
Type
journal article
Language
en
Open access
bronze

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Managing Conflict in Software Development Teams: A Multilevel Analysis. https://app.cochat.ai/papers/10.1016/s0737-6782(98)00011-3
The paper
Gobeli, D. H., Koenig, H. F., & Bechinger, I. (1998). Managing Conflict in Software Development Teams: A Multilevel Analysis. Journal of Product Innovation Management. https://doi.org/10.1016/s0737-6782(98)00011-3

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.