Skip to content
#software testing Open access

Conformal Effort Intervals: Distribution-Free Prediction Intervals for Software Effort and Their Empirical Reliability under Deployment Shift

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

Abstract

Replication package for Conformal Effort Intervals: Distribution-Free Prediction Intervals for Software Effort and Their Empirical Reliability under Deployment Shift. Conformal prediction turns any effort estimator into one that outputs an interval with a coverage guarantee that is distribution-free and holds for any base learner. Computing the nonconformity score in log space makes the interval multiplicative, ŷ×[1/k, k], which matches the right-skewed geometry of effort: a task predicted at 10 hours with k = 2.5 gives [4, 25] hours. The guarantee is marginal and conditional on exchangeability, which is what this study sets out to test. What the study found Across eight datasets, from four classical benchmarks to 59,934 tasks carrying a planner estimate: Under random splits, realized coverage is broadly consistent with nominal across four base learners and every level the calibration sets support Holding out an entire organization, a model without a human estimate covers 72.14% against a 90% target, with a worst fold of 62.07%, while a conformalized planner estimate averages 90.06% That failure is a calibration-transfer failure, not an irreducible limit: calibrating on 1,000 tasks from the target organization recovers the model arm to 90.22%, at roughly triple the interval width One column distributed with the China benchmark raises the share of estimates within 25% of actual from 24.24% to 96.04%, which an implausibly narrow interval exposes Against a historical empirical quantile, the finite-sample correction is the whole contribution, and it matters only when the calibration set is small: 90.34% against 85.51% at 20 calibration points, indistinguishable by 500 Contents src/ — the conformal module: split conformal, cross-conformal, CV+ and CQR, each documented with the guarantee it actually carries notebooks/ — six executable notebooks, including the definitive CESAW run results/ — every stored table and figure, with the script that produced each results/controlled/ — five controlled comparisons that isolate a confound in the main experiments: Mondrian calibration with the model held fixed, a common calibration sample across predictor arms, identifier coding, target-organization calibration, and the historical-quantile baseline results/superseded/ — earlier outputs kept for provenance; none backs a reported number data/raw/ — the four classical benchmarks, with provenance and leakage notes Verification Three scripts run here, and VERIFICATION.md records what each covers and what it does not. results/classical/check_reproduction.py re-runs the classical pipeline and compares its output against the stored tables; all six matched exactly at 20 repeats. check_sync.py fails if a notebook has fallen behind the committed modules. check_docs.py fails if a superseded figure reappears in the documentation. The dataset source is pinned to an upstream commit recorded in UPSTREAM-DATA-COMMIT.txt and checked out by the notebooks. Two analysis defects found after results had been produced are documented rather than removed. Requirements Python 3.10+, with requirements-lock.txt giving the exact versions used. The large datasets are cloned at runtime; the SEERA workbook must be downloaded separately from Zenodo. The full CESAW run takes about two hours.

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.