Oct 2026· Zenodo (CERN European Organization for Nuclear Research)
Expert finding and Q&A systems
Abstract
A pre-specification, not a result. This record deposits, before any Stack Overflow data is read for this design, the pre-registration of an observational test of a dating principle for knowledge. The principle holds that understanding of an object's mechanism is a sunk stock lost on the date the mechanism changes, for every holder at once, so a cheap substitute for expertise shows up in holders' exits and renewals at the object's next mechanism change rather than at the shock date. The rivals date the response by the shock (demand), by each holder's own asset (sunk-cost hysteresis), or by a calendar. Setting: Stack Overflow answerers of software-library questions after conversational models arrived (30 November 2022), with library major releases as mechanism changes. Confirmatory hypotheses: renewal at post-shock releases falls net of the flow margin (H1a), more in thin tags (H1b); a dark period exists after releases (H3-0). Placebos: a fake 2020 shock date, non-release question spikes, non-breaking minor releases, calendar-cadence libraries. Prior exposure to Stack Overflow outcomes (earlier deposited exercises and the published literature) is disclosed in full. Included: the registration, the literature-exposure check, the dated-predictions table, the blind theory derivations with reconciliation and priority checks, and the rule-first enumeration of candidate settings. Registry outputs, coder-agreement results and pre-period hashes follow as v1.1 before any post-shock row is read. All derivers, coders and readers are AI agents of one model family. SHA-256 manifest included.
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.