This disclosure-controlled reproducibility package accompanies the manuscript “Coworker networks, employee departures and staffing loss in three financial markets.” The study examines employee-departure patterns, coworker networks, staffing loss and firm-to-firm mobility across regulatory-register data from Hong Kong’s Securities and Futures Commission (SFC), the Australian Securities and Investments Commission (ASIC), and the United Kingdom’s Financial Conduct Authority (FCA).The package contains identifier-free aggregate results, numerical publication tables, figure-source data, synthetic test data, analysis and reporting code, configuration files, methodological protocols, publication figures, an environment specification, a file manifest and checksums. It supports exact regeneration of the released aggregate tables and reproduction of the publication figures.Raw regulatory records, personal or firm identifiers, appointment-level histories, row-level predictions and firm-level risk trajectories are not included. Full empirical model refitting requires the underlying regulatory records to be obtained lawfully from their respective providers and remains subject to provider terms. The included synthetic dataset supports checks of the expected schema and temporal logic but does not reproduce the empirical findings.The Figshare item-level licence is Creative Commons Attribution 4.0 International (CC BY 4.0). Original analysis software contained in src/ and run_reproduction.py is additionally licensed under the MIT License, as specified in LICENSE_CODE_MIT.txt and LICENSE_SCOPE.md. Author-created aggregate data, tables, figures, documentation and other research materials are licensed under CC BY 4.0. The original SFC, ASIC and FCA records are not included in this archive. Anyone seeking to use those records must obtain them independently and comply with the relevant regulator’s terms and applicable legal requirements.
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.