Knowledge Management Strategies and Processes in Agile Software Development: A Systematic Literature Review

Knowledge-intensive companies that adopt Agile Software Development (ASD) relay on efficient implementation of Knowledge Management (KM) strategies to promotes different Knowledge Processes (KPs) to gain competitive advantage. This study aims to explore how companies that adopt ASD implement KM strategies utilizing practices that promote the KPs in the different organizational layers. Through a systematic literature review, we analyzed 32 primary studies, selected by automated search and snowballing in the extant literature. To analyze the data, we applied narrative synthesis. Most of the identified KM practices implement personalization strategies (81 %), supported by codification (19 %). Our review shows that the primary studies do not report KM practices in the strategic layer and two of them in the product portfolio layer; on the other hand, in the project layer, the studies report 33 practices that implement personalization strategy, and seven practices that implement codification. KM strategies in ASD promote mainly the knowledge transfer process with practices that stimulate social interaction to share tacit knowledge in the project layer. As a result of using informal communication, a significant amount of knowledge can be lost or not properly transferred to other individuals and, instead of propagating the knowledge, it remains inside a few individuals minds.

💡 Research Summary

This paper conducts a systematic literature review (SLR) to investigate how organizations that adopt Agile Software Development (ASD) implement Knowledge Management (KM) strategies across different organizational layers and how these strategies support the four Knowledge Processes (KPs): creation, storage/retrieval, transfer/sharing, and application. The authors searched major academic databases using automated queries and complemented the search with snowballing, ultimately selecting 32 primary studies that met inclusion criteria (ASD adoption, explicit KM strategy description, and linkage to KPs). Data extraction focused on two KM strategy dimensions—personalization (human‑centric, informal interaction) and codification (formal documentation and repositories)—and mapped each identified practice to one of three organizational layers: strategic, product‑portfolio, and project.

The analysis reveals a pronounced dominance of personalization strategies: 81 % of the reported KM practices rely on informal, social mechanisms such as pair programming, daily stand‑ups, communities of practice, and ad‑hoc knowledge‑sharing sessions. Codification accounts for only 19 % and typically involves wikis, version‑controlled documentation, or dedicated knowledge bases. Notably, no KM practices were reported at the strategic layer, and only two appeared at the product‑portfolio layer, indicating a gap between high‑level corporate strategy and KM activities. In contrast, the project layer hosts 40 practices (33 personalization, 7 codification), suggesting that KM is largely a project‑level concern in agile contexts.

From the KP perspective, the majority of practices facilitate knowledge transfer (KT). Agile teams frequently rotate members, conduct sprint reviews, and rely on informal communication to disseminate tacit knowledge quickly. While this accelerates information flow, the authors caution that over‑reliance on informal channels can cause knowledge to remain siloed within a few individuals, leading to loss or mis‑transfer when team composition changes. The other KPs—knowledge creation (KC), storage/retrieval (KS), and application (KA)—receive comparatively less attention in the literature.

The discussion emphasizes the need for a balanced KM approach. Personalization aligns well with agile values of collaboration and adaptability, but codification provides the necessary scaffolding for long‑term knowledge retention and reuse. The authors propose a “strategy‑process‑practice” triangle: high‑level KM policies should be defined by senior management, translated into concrete practices at the project level, and supported by appropriate tools and cultural mechanisms. Without such alignment, organizations risk the “knowledge loss” problem highlighted in the abstract.

Limitations include the relatively small sample of primary studies, a bias toward academic publications (potentially under‑representing industry practice), and the qualitative nature of the narrative synthesis, which precludes quantitative assessment of KM impact on productivity, defect rates, or time‑to‑market. Future research directions suggested are large‑scale empirical studies measuring KM outcomes, investigations into the effectiveness of specific codification tools (e.g., AI‑enhanced knowledge bases), and case studies that document KM policy implementation at the strategic level.

In conclusion, the review finds that agile organizations predominantly employ personalization‑based KM practices at the project level, focusing on knowledge transfer. However, the absence of strategic‑level KM initiatives and the limited use of codification raise concerns about knowledge durability. To achieve sustainable competitive advantage, firms should integrate both personalization and codification strategies, align them with corporate objectives, and ensure that knowledge processes are supported across all organizational layers.