Explicit engagement and detailing of methods are not always expected or required practices within legal scholarship, as evidenced, for example, by the absence of method sections in many leading legal journals. Yet, methods provide the foundation to scholarship and its description facilitates the review of research reliability and validity. As a result of the oft-absent explicit engagement with methods in law, literature within other disciplines can inform legal scholars on, inter alia, methods outside traditional legal scholarship, their motivations, and their methodologies. Such practices, however, raise questions including: To what extent can legal scholars ‘transplant’ or adapt methods from other disciplines to research in law? How to effect such method transfers to legal research? What adjustments to methods are needed when transferring across disciplines? How are non-traditional legal scholarship methods received within law? This paper aims to contribute to these questions through a retrospective reflection on the author’s own experiences in undertaking scoping reviews within environmental law and their perceived acceptance (and at times lack thereof) in peer review processes. Scoping reviews were first used within health and medical sciences to identify, chart, and summarise data, but are now widely established in other fields. This paper first examines the value and limitations of scoping reviews as discussed in other disciplines, as well as within the context of legal scholarship. It then reflects on the challenges of using a non-legal research method based on the author’s own experiences. The paper concludes by summarising the lessons learnt from transferring a method across disciplines to inform other such adaptations.
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
It is proved that any global minimizer of the trajectory balance objective can define a policy that samples exactly from the target distribution, and empirically demonstrate the benefits of the trajectories balance objective for GFlowNet convergence, diversity of generated samples, and robustness to long action sequenc...
Esmeralda S. Whitammer, Moksh Jain, Emmanuel Bengio et al.· Neural Information Processin...· 302 citations· ⚡60
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
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.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.