Dynamics of Innovation in an “Open Source” Collaboration Environment: Lurking, Laboring and Launching FLOSS Projects on SourceForge

A systems analysis perspective is adopted to examine the critical properties of the Free/Libre/Open Source Software (FLOSS) mode of innovation, as reflected on the SourceForge platform (SF.net). This approach re-scales March’s (1991) framework and applies it to characterize the “innovation system” of a “distributed organization” of interacting agents in a virtual collaboration environment. The innovation system of the virtual collaboration environment is an emergent property of two “coupled” processes: one involves interactions among agents searching for information to use in designing novel software products, and the other involves the mobilization of individual capabilities for application in the software development projects. Micro-dynamics of this system are studied empirically by constructing transition probability matrices representing movements of 222,835 SF.net users among 7 different activity states. Estimated probabilities are found to form first-order Markov chains describing ergodic processes. This makes it possible to computate the equilibrium distribution of agents among the states, thereby suppressing transient effects and revealing persisting patterns of project-joining and project-launching.innovation systems, collaborative development environments, industrial districts, exploration and exploitation dynamics, open source software, FLOSS, SourceForge, project-joining, project-founding, Markov chain analysis.

Collaborative Requirements Engineering Notation for Planning Globally Distributed Projects

Requirements engineering represents a critical phase of the software development lifecycle in which requirements describing the functional and non-functional behaviors of a system are elicited, modeled, analyzed, negotiated, agreed, and specified. In traditional software systems these tasks are typically performed in face-to-face meetings between requirements engineers and the project level stakeholders. However, in today’s global software development environment, it is becoming increasingly commonplace for stakeholders to be dispersed across multiple geographical locations and time zones. Under these circumstances, face-to-face meetings become expensive, and often impossible to facilitate, and as a result the success of the requirements process relies, at least partially, on tools and processes that support distributed communication and collaboration. To investigate the challenges and effective practices for performing requirements activities in distributed environments, we conducted a series of in-depth interviews with project managers and business analysts who have worked with non-co-located stakeholders. Since many project managers fail to plan and deploy the necessary infrastructures to support quality communication, and in practice requirements are often elicited and managed via email exchanges; we introduced a visual modeling notation to help project managers proactively plan the collaboration infrastructures needed to support requirements-related activities in globally distributed projects. An underlying meta-model defines the elements of the modeling language, including locations, stakeholder roles, communication flows, critical documents, and supporting tools and repositories. The interview findings were further analyzed to identify practices that led to success or created significant challenges for the projects; resulting in a set of patterns for globally distributed requirements engineering

Coping with distance: An empirical study of communication on the Jazz platform

Global software development - which is characterized by teams separated by physical distance and/or time-zone differences - has traditionally posed significant communication challenges. Often these have caused delays in completing tasks, or created misalignment across sites leading to re-work. In recent years, however, a new breed of development environments with rich collaboration features have emerged to facilitate cross-site work in distributed projects. In this paper we revisit the question "does distance matter?" in the context of IBM Jazz Platform - a state-of-the-art collaborative development environment. We study the ecosystem of a large distributed team of around 300 members across 35 physical locations, which uses the Jazz platform for agile development. Our results indicate that while there is a delay in communication due to geographic separation, teams try to reduce the impact of delays by having a large percentage of work distributed within same/few time zones and working beyond regular office hours to interact with distributed teams. We observe different communication patterns depending on the roles of the team members, with component leads and project managers having a significantly higher overhead than development team members. We discuss the practical implications of our findings in terms of some best practices that can help lessen the impact of distance.</p

Exploring collaboration patterns among global software development teams.

This study examines communication behaviors in global software student teams. The authors of the paper characterize the types of communication behaviors that occur when student teams are engaged in a software development project. The authors present findings from a one-semester study that examined factors contributing to successful distributed programming interactions among students enrolled at the University of Atilim (Turkey), Universidad Tecnológica de Panamá, University of North Texas, and Middlesex University (UK). Using content and cluster analyses techniques, we identified distinct patterns of collaboration and examined how these patterns were associated with task, culture, GPA, and performance of collaborative teams. Our results suggest that communication patterns among global software learners may be related to task type, culture and GPA. It is hoped that these findings will lead to the development of new strategies for improving communication among global software teams

Dynamics of collaborative work in global software development environment.

This study aims to explore the dynamics of collaborative work in global software development projects. The study explored the nature of collaboration, the patterns of collaborative behaviors in different tasks in computer science, and the impact of the tasks to the collaboration among students. Four different collaborative software development tasks were assigned to the globally distributes teams. The study used data from 230 students from five universities, namely Atilim University (Turkey), Middle East Technical University (Turkey), Universidad Tecnológica de Panamá (Panama), University of North Texas (US), and Middlesex University (UK). The findings involve the recommendations for building effective collaborative working environments and guidelines for building collaborative virtual communities

Collaborative Development within Open Source Communities

Open source communities are one of the most successful-- and least appreciated--examples of high-performance collaboration and community building on the Internet today. Open source communities began as loosely organized, ad-hoc communities of contributors from all over the world who shared an interest in meeting a common need. However, the organization of these communities has proven to be very flexible and capable of carrying out all kind of developments, ranging from minor projects to huge programs such as Apache (Höhn, & Herr, 2004; Mockus, Fielding, & Herbsleb, 2005

Detecting Coordination Problems in Collaborative Software Development Environments

Software development is rarely an individual effort and generally involves teams of developers collaborating to generate good reliable code. Among the software code there exist technical dependencies that arise from software components using services from other components. The different ways of assigning the design, development, and testing of these software modules to people can cause various coordination problems among them. We claim\ud that the collaboration of the developers, designers and testers must be related to and governed by the technical task structure. These collaboration practices are handled in what we call Socio-Technical Patterns.\ud The TESNA project (Technical Social Network Analysis) we report on in this paper addresses this issue. We propose a method and a tool that a project manager can use in order to detect the socio-technical coordination problems. We test the method and tool in a case study of a small and innovative software product company