Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
This release brings the public software archive up to the current major-revision analysis and provides the matching Oklahoma paper-reproduction workflow. The companion results v2 contains Oklahoma job 8804859 plus its ATE backfill: 818 post-treatment events, a 250-day temporal cutoff, 512 attempted bootstrap replicates, and the 100-day observed-AOI-versus-none contrast. Expected saved counts are -51.508 for the naive fit and +175.200 for SEM. The main simulation and 67-scenario robustness results remain frozen. Explicitly select observed-versus-none for Oklahoma figures and tables, rejecting unavailable contrasts. Regenerate count and partition-sensitivity tables directly from saved fits, with full-precision CSV summaries. Freeze county geometry, resolve archived robustness paths locally, and support paths containing spaces. Regenerate publication assets during archive staging; validate canonical results and include a source manifest and per-file checksums. Document fitting settings, bootstrap recentering, stationary-rate reporting and the different simulation/application intervention conventions. Reproduction commands and limitations are in inst/zenodo/README.md. The archived univariate all-treated simulation omits control-history descendants, and its reference truth follows that same convention; the Oklahoma bivariate implementation retains the supplied pretreatment history. This release documents the frozen calculation and does not change the scientific model or rerun the studies. Validation: full figure/table reproduction from a staged archive; checks of canonical Oklahoma counts, bootstrap retained counts and all 67 scenarios; focused contrast-selection, bivariate ATE dispatch/KDE-cache and truncated-Omori tests. Source was tested with the existing compiled library; a fresh local native build was unavailable because this machine's Xcode licence has not been accepted.
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.· arXiv.org· 727 citations· ⚡54
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.· Empirical Software Engineeri...· 401 citations· ⚡48
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.· Information and Software Tec...· 394 citations· ⚡54
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· IET Software· 238 citations· ⚡9
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.· Journal of Systems and Softw...· 236 citations· ⚡13
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.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
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.
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…
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.