Understanding the attitudes, knowledge sharing behaviors and task performance of core developers: A longitudinal study

Abstract

Context: Prior research has established that a few individuals generally dominate project communication and source code changes during software development. Moreover, this pattern has been found to exist irrespective of task assignments at project initiation. Objective: While this phenomenon has been noted, prior research has not sought to understand these dominant individuals. Previous work considering the effect of team structures on team performance has found that core communicators are the gatekeepers of their teams' knowledge, and the performance of these members was correlated with their teams' success. Building on this work, we have employed a longitudinal approach to study the way core developers' attitudes, knowledge sharing behaviors and task performance change over the course of their project, based on the analysis of repository data. Method: We first used Social Network Analysis (SNA) and standard statistical analysis techniques to identify and select artifacts from ten different software development teams. These procedures were also used to select central practitioners among these teams. We then applied psycholinguistic analysis and directed content analysis (CA) techniques to interpret the content of these practitioners' messages. Finally, we inspected these core developers' activities as recorded in system change logs at various points in time during systems' development. Results: Among our findings, we observe that core developers' attitudes and knowledge sharing behaviors were linked to their involvement in actual software development and the demands of their wider project teams. However, core developers appeared to naturally possess high levels of insightful characteristics, which became evident very early during teamwork. Conclusion: Project performance would likely benefit from strategies aimed at surrounding core developers with other competent communicators. Core developers should also be supported by a wider team who are willing to ask questions and challenge their ideas. Finally, the availability of adequate communication channels would help with maintaining positive team climate, and this is likely to mitigate the negative effects of distance during distributed developments.

Exploring Knowledge Loss in Open Source Software (OSS) Projects

“…It is argued that contributors in OSS communities involve in free advice and tacit knowledge sharing to a larger extent than formal CSS organisations [42]. In OSS communities knowledge sharing can be associated to social motivation [43]. Social motivation such as supportive behaviour influences the behaviour of contributors and their performance.…”

A case study on software vulnerability coordination

“…Both limit also the applicability of common theoretical interpretations. For instance, knowledge sharing is a typical way to motivate research on open source social networks [50,57,109], but sharing of knowledge was not the main purpose of the oss-security mailing list during the period studied.…”

Causes of Architecture Changes: An Empirical Study through the Communication in OSS Mailing Lists

“…Core developers refer to those that are actively involved in high levels of communication and knowledge sharing in development [26] (i.e., architecture information communication in this work), e.g.,…”