Sep 2026· International Journal of Science and Research (IJSR)· pp. 848-853
Abstract
Large language model (LLM) agents are nondeterministic: the same task, run twice under identical conditions, may succeed once and fail once. The agent-evaluation literature has begun to measure this- most directly through the pass^k metric introduced with τ-bench- but treats it as a novel phenomenon. It is not. Software engineering has studied the same phenomenon under the name flaky tests since at least 2014, and has produced a root-cause taxonomy, detection algorithms, cost models, and CI-level management policy. This paper argues that agent evaluation should import that body of work. We give a structural mapping from established flaky-test root causes to sources of agentic nondeterminism, showing the correspondence is mechanistic rather than metaphorical: batch-noninvariant GPU kernels are the agentic form of floating-point reduction-order flakiness. Building on the latent-success representation of recent Markov-chain reliability work, we prove that pass^k converges as k → ∞ to the agent's deterministic pass rate D, and is flat in k if and only if no task is flaky. This yields the Flake Gap Φ = pass^1? D: the portion of a benchmark score an agent cannot reproduce on demand. Finally we show Φ is not identifiable from currently published numbers-fitting a zero-and-one- inflated Beta latent model to reported τ-bench results constrains D only to [0.00, 0.42] on τ-retail, leaving the deployable pass rate uncertain by 61% of the headline score. Benchmarks should therefore publish per-task trial counts rather than aggregate pass^k
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
Microsoft Research Blog· microsoft.comOct 12, 2026
StudentSim is a research system for evaluating and improving AI tutoring tools before they are tested with learners. It models how individuals may engage with tutors, giving feedback to improve tutor performance across subjects like chess, writing, and mathematics. The post Simulating student learning for better AI tutoring appeared first on Microsoft Research.
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…
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.