Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Research artifact accompanying manuscript V8.8, C-SDVR: Action Semantics for Contract-Aware Recovery in Repository Agents. The study characterizes when a second recovery seed produces a redundant or distinct projected candidate and evaluates fair fixed-action recovery controls. It does not establish practical success-rate or cost superiority. This version contains the corrected frozen recovery analyses; separately reported original and three-stage external action audits; a seven-operation executor extension checked against independent native regular-file execution; and a fresh 40-program QuixBugs pilot with 48 actual DeepSeek API requests. The fresh pilot yields identical outcomes across five policies: 38 audited successes, zero false accepts, and two stops, including 36 shared initial exits and two recovered failures. All observed states equal their projections, so no extra-branch benefit was observed. Small challenge programs, authored finite configurations, and observational logs are not treated as independent real-project recovery defects. The release includes version-pinned sources, raw and derived results, protocol and selection seeds, request/test receipts, executable checks, manuscript sources, figures, and file hashes. Older internal revision records and downloaded related-work full texts are excluded. The original version-5 scientific subset is preserved byte-for-byte with donor provenance. API keys are excluded. Licensing: author-owned original research code is MIT; author-owned original measurements and authored metadata are CC BY 4.0. Third-party code, datasets, model-output/source excerpts, and journal templates retain their original terms. See LICENSE_SCOPE.md and source-specific notices. Manuscript prose is not automatically included in the software/data license grants. This version supersedes the earlier artifact for the current manuscript evidence. The earlier DOI 10.5281/zenodo.21359453 remains the identifier for v1.0.0, not for these new analyses. The public development repository may lag this immutable deposit.
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.