Exploring the Impact of Socio-Technical Core-Periphery Structures in Open Source Software Development

In this paper we apply the social network concept of core-periphery structure to the sociotechnical structure of a software development team. We propose a socio-technical pattern that can be used to locate emerging coordination problems in Open Source projects. With the help of our tool and method called TESNA, we demonstrate a method to monitor the socio-technical core-periphery movement in Open Source projects. We then study the impact of different core-periphery movements on Open Source projects. We conclude that a steady core-periphery shift towards the core is beneficial to the project, whereas shifts away from the core are clearly not good. Furthermore, oscillatory shifts towards and away from the core can be considered as an indication of the instability of the project. Such an analysis can provide developers with a good insight into the health of an Open Source project. Researchers can gain from the pattern theory, and from the method we use to study the core-periphery movements

The Mirroring Hypothesis: Theory, Evidence and Exceptions

The mirroring hypothesis predicts that the organizational patterns of a development project (e.g. communication links, geographic collocation, team and firm co-membership) will correspond to the technical patterns of dependency in the system under development. Scholars in a range of disciplines have argued that mirroring is either necessary or a highly desirable feature of development projects, but evidence pertaining to the hypothesis is widely scattered across fields, research sites, and methodologies. In this paper, we formally define the mirroring hypothesis and review 102 empirical studies spanning three levels of organization: within a single firm, across firms, and in open community-based development projects. The hypothesis was supported in 69% of the cases. Support for the hypothesis was strongest in the within-firm sample, less strong in the across-firm sample, and relatively weak in the open collaborative sample. Based on a detailed analysis of the cases in which the mirroring hypothesis was not supported, we introduce the concept of actionable transparency as a means of achieving coordination without mirroring. We present examples from practice and describe the more complex organizational patterns that emerge when actionable transparency allows designers to 'break the mirror.'Modularity, innovation, product and process development, organization design, design structure, organizational structure, organizational ties

Exploring the Duality between Product and Organizational Architectures: A Test of the Mirroring Hypothesis

A variety of academic studies argue that a relationship exists between the structure of an organization and the design of the products that this organization produces. Specifically, products tend to "mirror" the architectures of the organizations in which they are developed. This dynamic occurs because the organization's governance structures, problem solving routines and communication patterns constrain the space in which it searches for new solutions. Such a relationship is important, given that product architecture has been shown to be an important predictor of product performance, product variety, process flexibility and even the path of industry evolution. We explore this relationship in the software industry. Our research takes advantage of a natural experiment, in that we observe products that fulfill the same function being developed by very different organizational forms. At one extreme are commercial software firms, in which the organizational participants are tightly-coupled, with respect to their goals, structure and behavior. At the other, are open source software communities, in which the participants are much more loosely-coupled by comparison. The mirroring hypothesis predicts that these different organizational forms will produce products with distinctly different architectures. Specifically, loosely-coupled organizations will develop more modular designs than tightly-coupled organizations. We test this hypothesis, using a sample of matched-pair products. We find strong evidence to support the mirroring hypothesis. In all of the pairs we examine, the product developed by the loosely-coupled organization is significantly more modular than the product from the tightly-coupled organization. We measure modularity by capturing the level of coupling between a product's components. The magnitude of the differences is substantial - up to a factor of eight, in terms of the potential for a design change in one component to propagate to others. Our results have significant managerial implications, in highlighting the impact of organizational design decisions on the technical structure of the artifacts that these organizations subsequently develop.Organizational Design, Product Design, Architecture, Modularity, Open-Source Software.

A brief method to assess the association of socio and technical dependencies on software quality

No AbstractKeywords: socio-technical congruence; actual coordination; coordination requirements; software engineering projects; software qualit

Evaluation of team dynamic in Norwegian projects for IT students

The need for teaching realistic software development in project courses has increased in a global scale. It has always been challenges in cooperating fast-changing software technologies, development methodologies and teamwork. Moreover, such project courses need to be designed in the connection to existing theoretical courses. We performed a large-scale research on student performance in Software Engineering projects in Norwegian universities. This paper investigates four aspects of team dynamics, which are team reflection, leadership, decision making and task assignment in order to improve student learning. Data was collected from student projects in 4 years at two universities. We found that some leader's characteristics are perceived differently for female and male leaders, including the perception of leaders as skilful workers or visionaries. Leadership is still a challenging aspect to teach, and assigned leadership is probably not the best way to learn. Students is are performing well in task review, however, needs support while performing task assignment. The result also suggests that task management to be done in more fine-grained levels. It is also important to maintain an open and active discussion to facilitate effective group decision makings

Challenges of Client-Vendor Relationships in Information Technology Outsourcing Engagements: An Interpretive Structural Modelling Approach

The client-vendor relationship is a key success factor for information technology outsourcing projects. Although many studies have been published about this concept, many of them have focused on a set of particular elements and have not investigated the relationship and dependencies between them. This research paper provides an overview about existing challenges for client-vendor relationships and discovers relationships between them by applying the ISM methodology. We conducted a literature research to gather and analyze relevant articles and identified 11 relevant challenges. Based on the literature research and 20 questionnaire responses we gathered from experts, we used interpretive structural modelling to discover the relevance and the contextual relationships among the identified challenges. The findings of this study reveal that three challenges, namely (1) lack of experience, (2) lack of good management practices and processes, and (3) lack of contractual objects can be treated as key elements for establishing a client-vendor relationship. We discuss further research directions and explain why all other identified challenges have high dependencies on each other