Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
We describe the document-reading model behind Money Maxer, an agent finance team that closes a simulated month for a mid-market software company. The system's premise is that no agent is trusted: every journal entry is re-performed by a small deterministic kernel before it can post. Inside that design we ask how small, cheap and local the model that reads finance documents can be. We LoRA-fine-tune open-weight models from 0.6B to 20B parameters on 956 synthetic documents and evaluate on NorthwindBench, a benchmark we built with a time split, held-out customers and vendors, and held-out document templates. With no schema in its prompt, the fine-tuned Qwen3-4B reaches 0.972 field-F1 and 100% schema validity on 120 test documents, up from 0.061 and 0% for the same model untouched. Four frontier Claude models given the full schema in every prompt score 0.943 to 0.958. At n=120 that gap is within noise, so our claim is parity, not superiority: a model that runs on one desktop matches frontier extraction quality at an estimated $0.15 to $0.40 per million generated tokens, against $5 to $50 for the frontier models. A fine-tuned 0.6B matches the 4B on the benchmark at three times the speed. Through the real kernel and ledger, the tuned reader settles exactly the 168 of 200 remittances that gold labels settle, with zero wrong postings. We report the unflattering results too: the 20B is the weakest of the family, the 0.6B fails on long invoices, and the benchmark is synthetic and self-built. Built at HackMIT 2026. Code and data: https://github.com/Preet37/money-maxing
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.