Spreadsheet disasters have been documented for more than thirty years, but they have not gone away. This paper examines the EuSpRIG horror stories archive as evidence of how ordinary spreadsheets fail and the consequences that follow. After cleaning and deduplication, 121 incidents from 1995 to 2026 were classified into twelve failure categories and analysed by mechanism, context and consequence. Formula errors, data-entry slips and data-handling mistakes account for 71 cases and recur across the whole period, from Fidelity's missing minus sign in 1995 to a mistyped date that cost Norway's sovereign wealth fund about $92 million in 2024. A second pattern concerns information present in a workbook but not visible to the recipient: hidden rows, hidden sheets, pivot-table caches, embedded objects and retained source layers can cause harm even when no calculation is wrong. The clearest rise in reported cases is in this hidden or embedded data category, whose most serious example is the 2022 Ministry of Defence spreadsheet that exposed details of roughly 18,700 Afghan applicants through hidden rows. The paper argues that spreadsheet risk is no longer only a problem of wrong numbers. It also involves visibility, disclosure, governance and trust. Existing taxonomies remain useful for formula, entry and handling errors, but do not fully capture the public harm caused by spreadsheets used as uncontrolled operational infrastructure. The same mistakes have persisted for three decades, what has changed is the authority organisations give to the spreadsheets that contain them.
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 perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 7, 2026
Students in MIT’s Concourse program delve deeply into the human condition, debate challenging questions, and learn to develop judgment about issues that can’t be quantified.
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
MIT News · Artificial Intelligence· news.mit.eduSep 30, 2026
Able to defeat top-ranked human players and more efficient than other models, the new system could help decision-makers in military maneuvers or business negotiations.