Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Copilot CLI Local Memory v1.1.2 — Citation and provenance This release makes the project's authorship, design history, and public release chronology explicit and machine-readable. It does not change the plugin's runtime behaviour. What changed Added CITATION.cff so GitHub, Zenodo, reference managers, and researchers can identify and cite the software consistently. Added DESIGN-AND-PROVENANCE.md to record the implemented design, public release chronology, and relationship to earlier Copilot memory proposals. Added Shankar Balakrishna to the MIT copyright notice. Linked the citation and provenance records from the README. Prepared the release for independent preservation through Zenodo and Software Heritage. The provenance document deliberately acknowledges earlier public proposals for persistent and local Copilot memory. The contribution recorded here is this project's concrete implementation: explicit save, search, and delete commands over plain local modular-instruction files, with deterministic search, optional file scopes, duplicate and common-secret detection, and no database or server. Verification All 11 automated tests pass. The Agent Plugins v1.0.0 manifest checks pass. CITATION.cff validates against the Citation File Format 1.2.0 schema. Runtime behaviour is unchanged from v1.1.1. Install or update copilot plugin install shankarnarayanb/copilot-cli-local-memory copilot --experimental Verify the plugin with /plugin list and /extensions manage. Full Changelog: https://github.com/shankarnarayanb/copilot-cli-local-memory/compare/v1.1.1...v1.1.2
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 2, 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.