Knowledge management for distributed agile processes: models, techniques, and infrastructure

Holz, Harald; Melnik, Grigori; Schaaf, Martin

doi:10.1109/enabl.2003.1231423

Cited by 9 publications

(6 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…AK vaporization could cause the following problems in AGSD [53,54] : (1) poorly understood requirements and technical solutions;…”

Section: Architectural Knowledge Vaporization Consequences In Agile and Global Software Developmentmentioning

confidence: 99%

“…Implementing the AK Condensation concept could help reduce AK vaporization in AGSD environments, taking into account the global and distribution aspects, without affecting the teams' agility. Furthermore, by reducing AK vaporization in AGSD, problems related to wasted time, software defects, and software projects' technical understanding [53,54] could be also reduced. It is worth recalling that we are presenting a single means to implement the concept of AK Condensation.…”

Section: Feasibility Of Ak Condensationmentioning

confidence: 99%

See 1 more Smart Citation

Towards a reduction in architectural knowledge vaporization during agile global software development

Borrego

Morán

Palacio³

et al. 2019

Information and Software Technology

View full text Add to dashboard Cite

“…AK vaporization could cause the following problems in AGSD [53,54] : (1) poorly understood requirements and technical solutions;…”

Section: Architectural Knowledge Vaporization Consequences In Agile and Global Software Developmentmentioning

confidence: 99%

Section: Feasibility Of Ak Condensationmentioning

confidence: 99%

Towards a reduction in architectural knowledge vaporization during agile global software development

Borrego

Morán

Palacio³

et al. 2019

Information and Software Technology

View full text Add to dashboard Cite

“…The pilot took place during the week commencing on March 23th, 2012. Data gathered in this step also helped us to verify the suitability of the statistical tests chosen for analyzing the data and the statistical tool called R 6 . After corrections made to improve the understanding of the questions and assertions, we created a new version of the questionnaire, which was sent to seven different companies.…”

Section: Data Collectionmentioning

confidence: 99%

“…surveymonkey.com/6 The R Project for Statistical Computing is available at http://www.r-project.org/…”

mentioning

confidence: 99%

The Influence of Organizational Factors on Inter-team Knowledge Sharing Effectiveness in Agile Environments

Santos

Goldman

Filho

et al. 2014

2014 47th Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

Agile software development is known by focusing on interaction among team members to share knowledge. However, little guidance is provided to encourage interaction across agile teams. Based on a preliminary conceptual model, this paper examines influencing factors, such as organizational strategy, and communication flow and channels, regarding inter-team knowledge sharing (KS) effectiveness in agile environments. We analyze the characteristics and the influence of the mentioned factors through a survey research method. Data was gathered from seven Brazilian agile software organizations. We employed statistical analysis techniques, e.g., structural equation modeling and cross-table analysis, to analyze the results. Within the surveyed companies, organizational strategy reflects on moderate commitment towards knowledge. KS practices are carried out to an acceptable standard. Extensive communication flow and the use of several channels denote that agile companies are also fostering interaction across teams. We found strong relationship between these factors and the companies' experience on agile methods. As companies continue on an agile adoption program, they growingly focus on long-term goals and consider knowledge as strategic resource. However, they still need to improve strategy alignment to all organization levels. Thus, we recommend that agile companies consider these factors when striving on this endeavor.

show abstract

“…Borrego et al [13] define architectural knowledge vaporisation as the loss of artefacts and architectural documents owed to poor documentation. The fact of not having this knowledge generates the following problems [14, 15]: (i) poor understanding of the requirements and technical solutions; (ii) knowledge transfer deficiency among developers; (iii) evolution and maintenance drawbacks; and (iv) time wasted by developers while searching for artefacts or experts. These problems cause the increase of time and cost in software development projects [16].…”

Section: Introductionmentioning

confidence: 99%

Ontology for knowledge condensation to support expertise location in the code phase during software development process

et al. 2020

View full text Add to dashboard Cite

Software Development is a complex process, in which every software product is a knowledge representation of all the involved people. In agile software development, knowledge is prone to vaporise, because documentation is not a priority as indicated in the agile manifesto. This condition generates problems such as poor understanding of the requirements, knowledge transfer deficiency among developers, time wasted by developers while searching for knowledge. The objective of this work is to reduce architectural knowledge vaporisation by means of knowledge condensation to support expertise location (high-level knowledge at a given time). This through an ontology that will condensate the knowledge in the code phase. This study presents the description of an ontology development process following the Methontology Framework. Results show that the proposed ontology does not present incongruence or inconsistency and answers the competency questions correctly. The main contribution of this study is the ontology which brings several benefits such as a shared concept of the knowledge in the code phase and a way to link the artefacts (resources used by developers in the project) and the experts (artefacts provider).

show abstract

Knowledge management for distributed agile processes: models, techniques, and infrastructure

Cited by 9 publications

References 12 publications

Towards a reduction in architectural knowledge vaporization during agile global software development

Towards a reduction in architectural knowledge vaporization during agile global software development

The Influence of Organizational Factors on Inter-team Knowledge Sharing Effectiveness in Agile Environments

Ontology for knowledge condensation to support expertise location in the code phase during software development process

Contact Info

Product

Resources

About