Scaling and Internationalizing an Agile FOSS Project: Lessons Learned

Fellhofer, Stephan; Harzl, Annemarie; Slany, Wolfgang

doi:10.1007/978-3-319-17837-0_2

Cited by 4 publications

(5 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Providing communication, documentation, and guidelines for developers and also users is important for FOSS projects right from their start [18]. In the context of Catrobat, services and processes needed to be introduced to allow communication between distributed team-members and also ensure the flow of project relevant information [22]. Catrobat provides a variety of services to tackle these potential issues.…”

Section: Communicationmentioning

confidence: 99%

“…As an example, the project itself offers public instances of Jira and Confluence to track the development process and document the overall project structure. While the project in early times used IRC (Internet Relay Chat) for communication [22], Slack channels are now the main place of communication between contributors. These tools are commonly used in industry, fostering the technical skills of the contributing students [9].…”

Section: Communicationmentioning

confidence: 99%

See 1 more Smart Citation

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

Müller¹,

Schindler²,

Slany³

2019

Proceedings of the Annual Hawaii International Conference on System Sciences

Self Cite

View full text Add to dashboard Cite

Open source is widely used for educational purposes in higher education around the world. While many educators use open source resources for teaching, there seems to be few contributions to such projects of students as part of their university courses. In this work we present our experience on establishing open source development from student contributors as part of their university curriculum. Since 2010 more than 300 students from Graz University of Technology have been involved in the presented Catrobat project and have gained knowledge about agile software development as well as several related domains, e.g., project management, marketing, or graphical design. In this paper we provide detailed insights into the project's organization and evaluate in a study how students feel in this setting. As we conclude, bringing open source to university courses is an effective practical approach based on social learning and provides benefits for students and researchers.

show abstract

Section: Communicationmentioning

confidence: 99%

Section: Communicationmentioning

confidence: 99%

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

Müller¹,

Schindler²,

Slany³

2019

Proceedings of the Annual Hawaii International Conference on System Sciences

Self Cite

View full text Add to dashboard Cite

show abstract

“…For the remaining 6 (19%) publications [38][39][40][41][42][43] the distribution of the projects researched were not specified or unclear…”

Section: Types Of Distributed Teams 41 Distributed Team Members and / Or Distributed Teamsmentioning

confidence: 99%

“…Distributed across different countries; with time zone differences [38], [25], [12], [26], [27], [28], [18], [29], [19], [36], [39], [40], [23], [14] [16], [30], [17], [31], [13], [20], [42], [21], [26] 22…”

Section: Scale Of Physical Distributionmentioning

confidence: 99%

Challenges in Distributed Agile Software Development Environment: A Systematic Literature Review

2019

KSII TIIS

View full text Add to dashboard Cite

Due to increasing interest in distributed agile software development, there is a need to systematically review the literature on challenges encountered in the agile software development environment. Using the Systematic Literature Review (SLR) approach, 32 relevant publications, dated between 2013 and 2018 were selected from four electronic databases. Data from these publications were extracted to identify the key challenges across the system development life cycle (SDLC) phases, which essentially are short phases in each agile-based iteration. 5 types of key challenges were identified as impacting the SDLC phases; these challenges are Communication, Coordination, Cooperation, Collaboration and Control. In the context of the SLDC phases, the Communication challenge was discussed the most often (79 times, 33%). The least discussed challenges were Cooperation and Collaboration (26 times, 11% each). The 5 challenges occur because of distances which occur in distributed environment. This SLR identified 4 types of distances which contribute to the occurrence of these key challenges -physical, temporal, social-cultural and knowledge/experience. Of the 32 publications, only 4 included research which proposed new solutions to address challenges in agile distributed software development. The authors of this article believe that the findings in this SLR are a resource for future research work to deepen the understanding of and to develop additional solutions to address the challenges in distributed agile software development.

show abstract

“…These aspects made it necessary to introduce a role to keep track of, sort, prioritize issues independently from their origin. Catrobat already applies several individual agile methods and various chances and challenges of these methods were already discussed in the past [2,3,9]. Due to the positive experiences with agile principles, also this new role was supposed to be based on agile methodologies.…”

Section: Motivation To Introduce Product Ownersmentioning

confidence: 99%

Introducing Agile Product Owners in a FLOSS Project

Müller

Schindler

Slany

2019

IFIP Advances in Information and Communication Technology

Self Cite

View full text Add to dashboard Cite

and how it introduced agile product owners. Product owners communicate the product vision, provide a general direction, decide about features, and prioritize requirements that are implemented by the community, i,e., they are ultimately responsible for the product. This agile approach is intended to ensure a certain outcome, such as business objectives, but also to react to the needs of community members and users on a short-term basis. This paper presents how therefore this role has been defined and the processes have been adapted.

show abstract

Scaling and Internationalizing an Agile FOSS Project: Lessons Learned

Cited by 4 publications

References 10 publications

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

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

Challenges in Distributed Agile Software Development Environment: A Systematic Literature Review

Introducing Agile Product Owners in a FLOSS Project

Contact Info

Product

Resources

About