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.
DevSecOps is a software development paradigm that places a high emphasis on the culture of collaboration between developers (Dev), security (Sec) and operations (Ops) teams to deliver secure software continuously and rapidly. Adopting this paradigm effectively, therefore, requires an understanding of the challenges, best practices and available solutions for collaboration among these functional teams. However, collaborative aspects related to these teams have received very little empirical attention in the DevSecOps literature. Hence, we present a study focusing on a key security activity, Application Security Testing (AST), in which practitioners face difficulties performing collaborative work in a DevSecOps environment. Our study made novel use of 48 systematically selected webinars, technical talks and panel discussions as a data source to qualitatively analyse software practitioner discussions on the most recent trends and emerging solutions in this highly evolving field. We find that the lack of features that facilitate collaboration built into the AST tools themselves is a key tool-related challenge in DevSecOps. In addition, the lack of clarity related to role definitions, shared goals, and ownership also hinders Collaborative AST (CoAST). We also captured a range of best practices for collaboration (e.g., Shift-left security), emerging communication methods (e.g., ChatOps), and new team structures (e.g., hybrid teams) for CoAST. Finally, our study identified several requirements for new tool features and specific gap areas for future research to provide better support for CoAST in DevSecOps.
Context: Effective coordination between different functional contributors is fundamental for the success of collaboration-focused software development paradigms such as DevSecOps. However, the quantification of coordination in such environments has received limited attention. Objectives: We introduce a Multi-Class Socio-Technical Congruence metric MC-STC by extending the application of the widely studied Socio-Technical Congruence STC framework to address the above gap. Our metric enables assessing coordination in a setting where contributors with different functional roles or alignments collaborate. Using a large-scale exploratory case study, we evaluate MC-STC for two classes (i.e., 2C-STC) Methods: We calculated 2C-STC for 100 systematically selected projects from the TravisTorrent dataset, considering developers (dev) and security-focused developers (sf-dev) as the two types of contributors with different functional alignments (i.e. two classes). We hypothesised that the dev and sf-dev interaction would have a quantifiable impact on the Vulnerability Score (VS) of each project. Results: Our results show a moderate negative association between 2C-STC and VS, with the Spearman correlation reaching -0.427 (p = 0.00000624), indicating that higher levels of coordination between dev and sf-dev led to projects with a lower incidence of high-severity vulnerabilities. In addition, 2C-STC shows a stronger negative relationship with VS than STC, suggesting that it is the more sensitive indicator of this relationship. Conclusion: The specific instantiation of our proposed metric, 2C-STC, performs comparatively better than STC for measuring cross-functional coordination in our selected projects. However, further research is needed to explore its broader applicability.
Context: DevOps has become one of the fastest-growing software development paradigms in the industry. However, this trend has presented the challenge of ensuring secure software delivery while maintaining the agility of DevOps. The efforts to integrate security in DevOps have resulted in the DevSecOps paradigm, which is gaining significant interest from both industry and academia. However, the adoption of DevSecOps in practice is proving to be a challenge. Objective: This study aims to systemize the knowledge about the challenges faced by practitioners when adopting DevSecOps and the proposed solutions reported in the literature. We also aim to identify the areas that need further research in the future. Method: We conducted a Systematic Literature Review of 54 peer-reviewed studies. The thematic analysis method was applied to analyze the extracted data. Results: We identified 21 challenges related to adopting DevSecOps, 31 specific solutions, and the mapping between these findings. We also determined key gap areas in this domain by holistically evaluating the available solutions against the challenges. The results of the study were classified into four themes: People, Practices, Tools, and Infrastructure. Our findings demonstrate that tool-related challenges and solutions were the most frequently reported, driven by the need for automation in this paradigm. Shift-left security and continuous security assessment were two key practices recommended for DevSecOps. Conclusions: We highlight the need for developer-centered application security testing tools that target the continuous practices in DevSecOps. More research is needed on how the traditionally manual security practices can be automated to suit rapid software deployment cycles. Finally, achieving a suitable balance between the speed of delivery and security is a significant issue practitioners face in the DevSecOps paradigm.