Skip to main content
  • Mexico
Nowadays, Agile and Global Software Development (AGSD) has brought benefits and new challenges to the software industry. Among the main challenges is Architecture Knowledge Management (AKM), due to the following reasons: (i) in Agile... more
Nowadays, Agile and Global Software Development (AGSD) has brought benefits and new challenges to the software industry. Among the main challenges is Architecture Knowledge Management (AKM), due to the following reasons: (i) in Agile Software Development team members prefer to convey knowledge in a face-to-face manner, over transmitting it through formal documents; and (ii) an efficient AKM in Global Software Development involves managing explicit knowledge. These opposite paradigms turn AKM into an unsolved issue in AGSD. In this study, the authors present a systematic mapping review about AKM in AGSD. From this review, they identified nine approaches that AGSD companies use to overcome the AKM challenge, which are grouped in three areas: (i) documentation artefact-based, (ii) communication-based, and (iii) methodological-based. Also, they found that the selected papers evenly support the three phases of the integrated knowledge management cycle (creation/capture, sharing/dissemination and acquisition/application), although only 7% of them support the capture of architectural knowledge in a formalised way. Finally, they conclude proposing critical points to consider in the implementation of AKM solutions in AGSD, and presenting their directions of future work.
Research Interests:
An important challenge in Agile Global Software Development (AGSD) is architectural knowledge vaporization, i.e., the loss of technical knowledge due to a lack of documentation. In a previous work we identified that technical knowledge is... more
An important challenge in Agile Global Software Development (AGSD) is architectural knowledge vaporization, i.e., the loss of technical knowledge due to a lack of documentation. In a previous work we identified that technical knowledge is usually available in unstructured textual electronic means (e.g. chat, mail, blogs, etc. – also known as
UTEMs) used by AGSD workers during development, although not necessarily easily accessible. Also, we proposed the concept of Knowledge Condensation as a means to recover knowledge from UTEMs, by introducing a structure to their contents along with means to retrieve knowledge. In this work we present our first step towards a Knowledge Condensation tool, through a prototype tagging mechanism to structure
architectural knowledge during UTEM interactions. We evaluated the prototype and obtained the following results: (1) a high perception of usefulness and a high projected intention of use; and (2) the identification of 6 tagging behavior profiles from participants. These tagging behaviors can be grouped as (i) participants who tag as expected, (ii) participants who tag more than expected, and (iii) participants who tag less than expected. These results suggest that it is important to cope with “little or no tagging” and “excessive tagging” behaviors to implement knowledge condensation based on UTEM tagging. Furthermore, we identified that tagging could be a good option
to structure UTEM interactions, and to retrieve architectural knowledge from UTEM logs. Future work includes improving the tagging mechanism prototype based on the participants’ suggestions and overall evaluation results, and implementing a searcher prototype to further evaluate the concept of knowledge condensation based on tagging of UTEM interactions.
Research Interests:
— Agile Global Software Development (AGSD) is a reality, since nowadays software products are required to get into the market with more speed than before. This situation has pushed Global Software Development (GSD) companies to adopt... more
— Agile Global Software Development (AGSD) is a reality, since nowadays software products are required to get into the market with more speed than before. This situation has pushed Global Software Development (GSD) companies to adopt lighter ways to develop software (Agile Software Development-ASD) to satisfy market demands. However, AGSD companies have encountered increased technical debt and architectural knowledge (AK) vaporization, mainly because the inherent differences between ASD and GSD, especially in documentation handling. This paper describes a research project in which it is proposed to exploit the AK that is recorded in unstructured textual electronic media (UTEM) generally used in AGSD, in order to decrease the problems of software evolution and maintenance, caused by a lack of adequate AK. Until now, the preliminary results of this research show that this approach could be feasible in AGSD environments.
— Nowadays, the use of agile methodologies (AM) in Global Software Development (GSD) – known as AGSD – is increasingly common. However, AM and GSD are not completely compatible. On the one hand, in AM people interactions (face-to-face)... more
— Nowadays, the use of agile methodologies (AM) in Global Software Development (GSD) – known as AGSD – is increasingly common. However, AM and GSD are not completely compatible. On the one hand, in AM people interactions (face-to-face) are preferred over document-based communications to share knowledge. On the other hand, in GSD knowledge sharing is conducted through documents to minimize the effect of the inherent four distances (physical, temporal, language and cultural). This means that tacit knowledge is preferred in AM and explicit knowledge is preferred in GSD. These differences between AM and GSD affect many aspects of software development, for instance: Architectural Knowledge Management. According to the literature, in AGSD it is preferred to convey Architectural Knowledge (AK) by frequent interactions across sites through unstructured and textual electronic media (UTEM) (chats, emails, forums, etc.), that is, AK is articulated in these media. UTEM leave a textual record of the transmitted information, thus leaving an unstructured log of the shared AK of the project. In this paper we present an empirical study to understand AK articulation in UTEM in AGSD teams. Our results consist of an ontology that represents the involved aspects in AK articulation in UTEM in AGSD teams. Additionally, we identified eleven categories of interactions across sites through UTEM, where requirements and coding themes are prominent. Finally, we found that AK in UTEM is perceived as important, regardless the interaction frequency. These results lead us to think that a tool to structure and exploit AK in UTEM is needed in AGSD, in order to bridge the gap between AM and GSD. Keywords— agile global software development; virtual teams; architectural knowledge; unstructured and textual electronic media.
—Many companies have adopted agile software development (ASD), mainly due to it can handle scarce requirements. However, some unsolved challenges exist in ASD, particularly in global software development (GSD) companies (known as AGSD).... more
—Many companies have adopted agile software development (ASD), mainly due to it can handle scarce requirements. However, some unsolved challenges exist in ASD, particularly in global software development (GSD) companies (known as AGSD). These challenges include ASD lax documentation contrasted by the methodological standardization required in GSD, due to its inherent distances. Lax documentation leads to documentation debt and architectural knowledge (AK) vaporization, which cause negative effects on the development process and on the product itself. In order to reduce these effects, we propose Scrumconix, a hybrid method that uses a lightweight approach to document in AGSD environments, which also aims to decrease the effect of linguistic and cultural distances. In addition, we present preliminary results of Scrumconix implementation in a Mexican AGSD company.