Understanding Knowledge Management in Agile Software Development Practice

Andriyani, Yanti; Hoda, Rashina; Amor, Robert

doi:10.1007/978-3-319-63558-3_17

Cited by 16 publications

(4 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, there is surprisingly little research on what takes place during such meetings and why and how the teams practices are adapted as a result. In a grounded theory study, Andriyani et al present a categorisation of what is discussed in retrospectives [1]. Others propose the use of these reflective meetings for software process improvement [27], or propose formats to improve their effectiveness [3].…”

Section: Methods In Software Engineeringmentioning

confidence: 99%

“…Our findings resonate with the existing literature on retrospective. The discussion of the stand-up meeting may also be described according to the categorizations developed in [1]: Initially raising the matter may be described as 'Reporting and Responding', the root-cause analysis and development of changes as 'Relating and Reasoning', and the decision about the action plan may be seen as 'Reconstructing'.…”

Section: Reflection Experimentation and Agile Improvementmentioning

confidence: 99%

See 1 more Smart Citation

Exploring the evolution of software practices

Dittrich

Michelsen

Tell

et al. 2020

Proceedings of the 28th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Softw

View full text Add to dashboard Cite

When software products and services are developed and maintained over longer time, software engineering practices tend to drift away from both structured and agile methods. Nonetheless, in many cases the evolving practices are far from ad hoc or chaotic. How are the teams involved able to coordinate their joint development? This article reports on an ethnographic study of a small team at a successful provider of software as a service. What struck us was the very explicit way in which the team adopted and adapted their practices to fit the needs of the evolving development. The discussion relates the findings to the concepts of social practices and methods in software engineering, and explores the differences between degraded behavior and the coordinated evolution of development practices. The analysis helps to better understand how software engineering practices evolve, and thus provides a starting point for rethinking software engineering methods and their relation to software engineering practice. CCS CONCEPTS • Software and its engineering → Agile software development; Programming teams; • Human-centered computing → Computer supported cooperative work.

show abstract

Section: Methods In Software Engineeringmentioning

confidence: 99%

Section: Reflection Experimentation and Agile Improvementmentioning

confidence: 99%

Exploring the evolution of software practices

Dittrich

Michelsen

Tell

et al. 2020

Proceedings of the 28th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Softw

View full text Add to dashboard Cite

show abstract

“…Our study was aimed to reveal the potential contribution of agile principles to KM education, KM RE, and KM solutions. As agile guidelines are regarded as principles that foster organizational flexibility and dynamic handling in various contexts [23,24,29,37], we claim that KM education should foster agile principles in both the KM education procedure itself and the implementation of KM in organizations. Based on the KM-REM methodology [8], a KM course was developed where the students employed project-based learning [18] integrated with agile practices [25,26].…”

Section: Agile Education Of Agile Kmmentioning

confidence: 99%

Agile-Based Education for Teaching an Agile Requirements Engineering Methodology for Knowledge Management

2021

View full text Add to dashboard Cite

The importance of the role that knowledge management (KM) plays in the success of knowledge-intensive organizations has long been acknowledged. However, requirements engineering (RE) methods for KM solutions still lack maturity, as do the educational programs in this domain. In this paper, an agile-based educational method for teaching RE for KM solutions, specifically an agile KM RE methodology (AKM-REM), is proposed. The paper reports a teaching experience, in which 17 teams of graduate students learned and implemented AKM-REM, each in a different real-life case study. Data were collected via class observations and from the students’ submitted projects and underwent qualitative content analysis. The findings demonstrate the manner in which AKM-REM creates a culture of collaboration, trust, and reflection, fostering the dynamic and flexible organization that is required in today’s competitive business environment. The contribution of this paper is fourfold. First, it presents an extension of the research on agile-based RE for KM solutions as a specialized area. Second, it presents an extension of an existing method KM-REM along the agile principles. Third, it provides means for agile-based education for analyzing and addressing KM challenges effectively. Finally, it describes the importance of agile KM RE in the context of sustainability.

show abstract

“…Several benefits and needs to apply KM in Software Engineering have been reported in several studies over the years [Bjørnson and Dingsøyr 2008], [Souza et al 2015], [Vasanthapriyan et al 2015], [Carreteiro et al 2016], [Andriyani et al 2017], [Maciel et al 2018b].…”

Section: Introductionmentioning

confidence: 99%

A Tool for Automation of Knowledge Management Diagnostics in Software Development Companies

Santos

Salgado

Souza

et al. 2019

Anais Estendidos Do X Congresso Brasileiro De Software: Teoria E Prática (CBSoft Estendido 2019)

View full text Add to dashboard Cite

Knowledge Management (KM) is responsible for using the intellectual resources of an organization. KM principles are both determining and effective factors for the software product quality. Several KM process have been proposed in the literature. However, for a KM initiative to be successful, it is important to consider the current state of KM activities in a company. In this context, the objective of this work is to measure KM activities in software engineering companies by means of a tool that automates the process of KM diagnosis. This paper presents the Software Engineering KNOWledge management diagnosis (SEKNOW) tool, its main functionalities, the potential users profile and examples of use. In addition, we show how the architecture was implemented in order to make the tool extensible to multiple diagnostics and how the companies can employ the tool to fetch data to their systems. Finally, we present similar tools and compare their functionalities.

show abstract

Understanding Knowledge Management in Agile Software Development Practice

Cited by 16 publications

References 11 publications

Exploring the evolution of software practices

Exploring the evolution of software practices

Agile-Based Education for Teaching an Agile Requirements Engineering Methodology for Knowledge Management

A Tool for Automation of Knowledge Management Diagnostics in Software Development Companies

Contact Info

Product

Resources

About