MétaCan
Menu
Back to cohort
Record W2604910628 · doi:10.25300/misq/2017/41.1.03

A Configural Approach to Coordinating Expertise in Software Development Teams1

2017· article· en· W2604910628 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueMIS Quarterly · 2017
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsMcGill University
Fundersnot available
KeywordsSoftware developmentSoftwareComputer scienceKnowledge managementProcess managementData scienceArtificial intelligenceEngineering

Abstract

fetched live from OpenAlex

Despite the recognition of how important expertise coordination is to the performance of software development teams, understanding of how expertise is coordinated in practice is limited. We adopt a configural approach to develop a theoretical model of expertise coordination that differentiates between design collaboration and technical collaboration. We propose that neither a strictly centralized, top-down model nor a largely decentralized approach is superior. Our model is tested in a field study of 71 software development teams. We conclude that because design work addresses ill-structured problems with diverse potential solutions, decentralization of design collaboration can lead to greater coordination success and reduced team conflict. Conversely, technical work benefits from centralized collaboration. We find that task knowledge tacitness strengthens these relationships between collaboration configuration and coordination outcomes and that team conflict mediates the relationships. Our findings underline the need to differentiate between technical and design collaboration and point to the importance of certain configurations in reducing team conflict and increasing coordination success in software development teams. This paper opens up new research avenues to explore the collaborative mechanisms underlying knowledge team performance.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.972
Threshold uncertainty score0.561

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.023
GPT teacher head0.274
Teacher spread0.251 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it