Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Background. RewardBench 2 aggregates pairwise preference accuracy across heterogeneous task families (factuality, instruction following, safety, and others). A single leaderboard score can mask systematic subset specialization, yet standard benchmark reporting rarely tests whether accuracy is independent of task category. Methods. We applied CONFIRM, a chi-square test of independence with Cramér's V effect sizing and empirically anchored letter grades, to 174 publicly released reward models. For each model we constructed a 5 × 2 contingency table (subset × correct/incorrect) from published per-prompt scores (n = 1,763 prompts after excluding the non-binary Ties subset). The null hypothesis was that correct/incorrect outcomes are independent of subset category. Grades A–F reflect V magnitude (CONFIRM v2 thresholds); grade I denotes insufficient power. Non-significant results grade F only when power ≥ 0.80 to detect V = 0.10. Results. All 174 models rejected independence at α = 0.05 (all p < 0.02; median V = 0.272, range 0.082–0.467). No model received F or I. Grade distribution: A 36.8% (n = 64), B 50.6% (n = 88), C 11.5% (n = 20), D 1.1% (n = 2). Pooling across models, mean per-subset accuracy was lowest on Precise IF (36.3 per 100) and highest on Safety (75.7 per 100). In 93.1% of models the largest subset gap involved Precise IF as the weakest category; Safety was the strongest endpoint in 70.7% of cases. Conclusions. Published RewardBench 2 reward models exhibit statistically detectable subset heterogeneity at this sample size. Aggregate accuracy therefore understates structured performance imbalance, particularly weakness on precise instruction-following relative to safety-oriented subsets. CONFIRM provides a reproducible heterogeneity diagnostic to be read alongside ranking metrics. Plain-language summary. For all 174 reward models tested, the rate of correct judgments differed across the five task types by more than the prespecified statistical threshold. The direction of the difference was shared: 93.1% of models were weakest on precise instruction-following, and 70.7% were strongest on safety. Each model was tested on 1,763 prompts, enough sensitivity to detect even a small difference had one been present, so a model showing no difference would have been identifiable as such. None did. A single overall leaderboard score does not show this — two models with the same average can differ substantially underneath. This analysis measures whether a model's accuracy is uneven across task types, not which model is best overall, and it identifies a pattern without establishing its cause. Supplementary material. The deposited archive (rewardbench2_validation.zip) contains per-model results, subset breakdowns, contingency cell counts, validation flags, and step-by-step mathematical derivations for all 174 models. Competing interests. The author is affiliated with TraceSeis, Inc., which is developing CONFIRM as a commercial product. This constitutes a competing interest. All results are reproducible from the cited public data and the deposited analysis outputs. AI use disclosure. Generative AI tools were used during preparation of this work, in two distinct roles. For drafting and implementation: Anthropic Claude assisted with manuscript prose; the CONFIRM engine and analysis pipeline were implemented with AI coding tools (Cursor, Anthropic Claude) to the author's specification; and Google Gemini was consulted during writing and analysis runs. For review: Perplexity provided editorial review of a late draft, and xAI Grok was used as a general consistency check. This reflects the author's record of tool use and is not offered as an exhaustive log. Research design, statistical methodology, and interpretation are the author's. Because the analysis software was AI-implemented, every reported statistic was independently recomputed from observed cell counts and checked against pipeline output before reporting; per-model derivations are deposited as confirm_math.html and can be checked by hand. The author takes full responsibility for the contents of this record.
Agile - denoting "the quality of being agile, readiness for motion, nimbleness, activity, dexterity in motion" - software development methods are attempting to offer an answer to the eager business community asking for lighter weight along with faster and nimbler software development processes. This is especially the case with the rapidly growing and volatile Internet software industry as well as for the emerging mobile application environment. The new agile methods have evoked substantial amount of literature and debates. However, academic research on the subject is still scarce, as most of existing publications are written by practitioners or consultants. The aim of this publication is to begin filling this gap by systematically reviewing the existing literature on agile software development methodologies. This publication has three purposes. First, it proposes a definition and a classification of agile software development approaches. Second, it analyses ten software development methods that can be characterized as being "agile" against the defined criterion. Third, it compares these methods and highlights their similarities and differences. Based on this analysis, future research needs are identified and discussed.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 728 citations· ⚡54
Context: Software startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present a unique combination of characteristics which pose several challenges to software development activities. Objective: This study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers. Method: We conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups. Results: A total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed. Conclusion: This mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, 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 growing literature on affect among software developers mostly reports on the linkage between happiness, software quality, and developer productivity. Understanding happiness and unhappiness in all its components -- positive and negative emotions and moods -- is an attractive and important endeavor. Scholars in industrial and organizational psychology have suggested that understanding happiness and unhappiness could lead to cost-effective ways of enhancing working conditions, job performance, and to limiting the occurrence of psychological disorders. Our comprehension of the consequences of (un)happiness among developers is still too shallow, being mainly expressed in terms of development productivity and software quality. In this paper, we study what happens when developers are happy and unhappy while developing software. Qualitative data analysis of responses given by 317 questionnaire participants identified 42 consequences of unhappiness and 32 of happiness. We found consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts. Our classification scheme, available as open data enables new happiness research opportunities of cause-effect type, and it can act as a guideline for practitioners for identifying damaging effects of unhappiness and for fostering happiness on the job.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
Mobile phones have been closed environments until recent years. The change brought by open platform technologies such as the Symbian operating system and Java technologies has opened up a significant business opportunity for anyone to develop application software such as games for mobile terminals. However, developing mobile applications is currently a challenging task due to the specific demands and technical constraints of mobile development. Furthermore, at the moment very little is known about the suitability of the different development processes for mobile application development. Due to these issues, we have developed an agile development approach called Mobile-D. The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduJul 13, 2026