Skip to content
#software testing Dataset Open access

Agent-Mediated Phase Transitions in Software Delivery: Search, Screening and Coding Data

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

Single-coder extraction, checked against an independent coder on a sample. First-pass screeningand coding were performed by a single coder. The 10% sample (dual_screen_sample = YES, n = 19,drawn with random.Random(7410238)) was screened twice, on two separate checks with differentepistemic value: Intra-coder test–retest — the same coder, in a fresh session and blind to its own first decision, reproduced 18 of 19 decisions: 94.7% agreement, Cohen's kappa = 0.883. This measures stability under repetition and cannot detect a bias shared by both passes. Inter-coder agreement — a second, independent coder (the author), blinded to the first pass, agreed on 14 of 19: 73.7% agreement, Cohen's kappa = 0.463 (moderate; SE 0.206; 95% CI 0.06–0.87). Five records were decided differently: A024, A034, A052 and A070 (first coder excluded, second coder admitted) and A150 (first coder admitted, second coder excluded). The second coder's decisions were adopted, so the included set is 65 of 194 in-window records; the four admitted records were coded on all eight facets. Both statistics are reported separately in 08_dual_screening.json, which marks inter_rater_agreement as the primary statistic and sets WARNING to null. 08_human_coder_decisions.csv records the second coder's decisions together with the first-pass decision and rule for each sampled record, so the statistics stay reproducible now that the adopted decisions sit in the corpus. The 19 sampled records carry a decision agreed by two coders; the remaining 175 carry the first coder's decision alone. The corpus is therefore screened to two standards, an asymmetry the manuscript states in Section 3.8 and carries into Section 6.2 as a threat to validity. Grey literature only, in this strand. arXiv is coded as grey literature and is never pooled withpeer-reviewed evidence. The eight peer-reviewed databases in Table 4 are pending institutional access; theirresults must be appended before the frequency tables are treated as the study's final result. Screening aid, not decision. 02_screening_sheet.csv is a keyword triage aid. The decisions in03_screening_decisions.csv were made on the abstract text by the coder; the aid's proposed bucket is retained only for transparency about how attention was allocated. Time window. Four records pre-date January 2023 and are excluded by the registered window. Terminology instability. The constructive threat registered in the protocol (Section VII) is observable in thedata: 04_analysis_RQ4_seed_crosswalk.csv shows Section V phenomena appearing under unrelated vocabulary, which is why single-term booleans under-recall this literature. v4 adopts the second coder's decisions into the corpus. The 10% sample was screened by the author as second coder; agreement with the first-pass decisions was 14 of 19 records (73.7%, Cohen's kappa = 0.463, moderate), against 18 of 19 (94.7%, kappa = 0.883) for the first coder's own blinded re-screen. The four records the second coder admitted (A024, A034, A052, A070) were coded on all eight facets and A150 was removed, so the corpus is now 65 included studies of 194; every count and table was recomputed. 08_human_coder_decisions.csv now also carries the first-pass decision and rule for each sampled record, so the reliability statistics stay reproducible after adoption. The manuscript reports both figures and treats their divergence as the study's principal limitation. Version 5 (28 September 2026) adds the peer-reviewed strand, its harvest, the second-coder measurement and the JSS revision material. Peer-reviewed strand (Amendment 3). The registered string was executed on open cross-publisher indexes — OpenAlex, with Crossref for the publisher-level verification — because the eight subscription databases named in the protocol are not accessible to the author. New here: data/strand_p/ (28 candidates with their strand label, 19 screening decisions each with its rule and a one-line rationale, the funnel and counts), data/open_harvest/ (the verified records and the unmodified raw grid responses), and the harvest, verification and figure code. The funnel: 147 records returned → 128 verified against all three blocks of the string → 42 peer-review types → minus 9 Zenodo deposits, 12 duplicates and 2 records already in the grey strand → 19 screened → 17 excluded (E1 15, E3 1, RQ1NEG 1) → 2 included, coded separately and never pooled with the grey strand. Second-coder measurement (Amendment 4). second_coder/ carries both packs as issued, the sample manifests, the independent coder's returned files and the scoring scripts; data/08b_second_coder_reliability.json reports the measured round — 40 of 40 screening decisions, 20 of 20 exclusion rules and 7 of 7 boundary classifications agreed, reported as raw agreement with a Clopper-Pearson one-sided 95% lower bound of 92.8% (kappa is degenerate at perfect agreement). The first, uncalibrated pilot round (47.5% agreement, kappa = -0.050) is retained in data/08b_pilot_v1_NOT_REPORTED.json as evidence about the instrument; it is not a reliability figure for the corpus. The independent coder is identified as "Coder 02" throughout, and the answer keys and the private correspondence are deliberately not included. Also in this version: the two-strand screening-flow figure with the numbers it draws on (figures/), the two-strand counts (data/flow_counts.json), the citation map for the revision (data/refs_jss_map.json), the SEGRESS alignment and amendment records (protocol/), 00_ADDENDUM_v5.md describing every addition, and MANIFEST_sha256.txt giving the SHA-256 digest of every file.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.