Can FOSS projects benefit from integrating Kanban: a case study

Abstract

Free and Open Source Software (FOSS) and Agile Software Development (ASD) have both been recognized as important software development methods; they have many success stories and share some similarities. However, there is a lack of research regarding the comprehensive integration of the two. This work presents a single case of a hybrid student FOSS project where ASD and FOSS were combined and reports if this combination benefits the contributors. We conducted Action Research (AR) with one sub-team of a large hybrid student FOSS project, and performed three AR cycles based on the Kanban method. The Kanban practices visualize the workflow, make policies explicit and implement feedback loops were examined during the AR cycles. They are discussed in detail in this paper, which has two main contributions: first, it describes a real world situation, where Kanban is applied to a hybrid student FOSS project, and second, it determines that the combination is experienced as beneficial by contributors. Study participants report a positive effect on communication with other teams and stakeholders due to the use of the Kanban and regard their time acquiring knowledge about Kanban practices as well spent.

Using a coach to improve team performance when the team uses a Kanban process methodology

“…The role could help the team understand their capabilities and help them think about possible improvements [58]. Harzl [59] noted the presence of a Kanban coach, and it was rated very beneficial by all team members, but a clear definition of a KC and his/her responsibilities was not clearly defined.…”

Engaging Students in Open Source: Establishing FOSS Development at a University

“…This trust is essential for contributors and the overall project, since mistrust may lead the entire project to collapse [20]. The general development and management approach of Catrobat is based on agile principles, e.g., eXtreme Programming [21]. Following these principles also fosters teamwork and guides the community towards a shared goal.…”

Strengths and Weakness of Traditional and Agile Processes - A Systematic Review

“…Agile methods and practices are often poorly implemented [1]. There are still several organizations who are struggling to adopt Agile methods successfully [8,10].…”

“…Pair programming and continuous integration are the most used practices in XP and results in improving the productivity [25]. XP works well with simple and small scale projects and focuses more on coding than on the design [10]. The weaknesses of XP as stated in [5] are lack of documentations, poor architectural structure and less focus on design.…”