Exploratory case study reveals a moderate negative correlation between coordination and vulnerability in projects, suggesting its importance.
Effective coordination between contributors with different functional roles is fundamental for the success of collaboration‐centric software development paradigms such as DevSecOps. However, quantitatively assessing coordination in such settings has received limited attention. We introduce multi‐class socio‐technical congruence (), an extension of the widely studied socio‐technical congruence () framework to address this gap. Our metric enables the assessment of coordination in a setting where contributors with different functional roles or alignments collaborate. Using a large‐scale exploratory case study, we evaluated for two classes (i.e., ). Specifically, we calculated for 100 systematically selected projects from the TravisTorrent dataset, considering developers ( dev ) and security‐focused developers ( sf‐devs ) as the two types of contributors with different functional alignments (i.e., two classes). We hypothesized that the dev and sf‐dev interaction would have a quantifiable impact on the vulnerability score () of each project. Our results show a moderate negative association between and , with the Spearman correlation reaching 0.427 (), indicating that higher levels of coordination between dev and sf‐dev led to projects with a lower incidence of high‐severity vulnerabilities. In addition, shows a stronger negative relationship with than , suggesting that it is the more sensitive indicator of this relationship. Therefore, the specific instantiation of our proposed metric, , performs comparatively better than for measuring cross‐functional coordination in our selected projects. However, further research is needed to explore its broader applicability.
No takes yet. Share an insight, caveat, or question.
Rajapakse et al. (2025) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: