MétaCan
Menu
Back to cohort
Record W2070430535 · doi:10.1109/ieem.2011.6118198

The impact of absorptive capacity on the ex-post adoption of agile methods: The case of Extreme Programming model

2011· article· en· W2070430535 on OpenAlexaff
B. Bahli, Y. Benslimanne, Zijiang Yang

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsYork University
Fundersnot available
KeywordsAgile software developmentMindsetExtreme programmingAbsorptive capacityComputer scienceContext (archaeology)Agile Unified ProcessProcess (computing)ScrumConstruct (python library)Dynamic capabilitiesSet (abstract data type)Process managementKnowledge managementNew product developmentSoftware engineeringSoftware developmentEngineeringSoftware development processBusinessSoftwareArtificial intelligence

Abstract

fetched live from OpenAlex

Agile development methods have emerged to overcome some of the process and product-related problems associated with traditional models. They are believed to be lightweight, people focused, adaptive and allow better information systems development (ISD) performance. Nevertheless, they require a significant capacity of absorbing new set of skills, knowledge and mindset changing. When using agile methods IS developers are faced with a challenge to quickly assimilate the mindset of these new methods and develop the ability to recognize information and apply it in context. This paper reports on two ex-post ISD project implementation. We integrate a central construct in the dynamic capability theory - absorptive capacity to explain agile method adoption and usage. The findings show that absorptive capacity, indeed, plays an important role in adopting and using agile method-Extreme Programming model. The implications of these findings for both researchers and practitioners are discussed.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.011
metaresearch head score (Gemma)0.046
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.011
Threshold uncertainty score0.058

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0110.046
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0020.005
Scholarly communication0.0050.006
Open science0.0010.004
Research integrity0.0010.003
Insufficient payload (model declined to judge)0.0040.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.147
GPT teacher head0.344
Teacher spread0.197 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designQualitative
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations4
Published2011
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207