DevOps Competences and Maturity for Software Producing Organizations

Feijter, Rico de; Overbeek, Sietse; Vliet, Rob van; Jagroep, Erik; Brinkkemper, Sjaak

doi:10.1007/978-3-319-91704-7_16

Cited by 25 publications

(32 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…We found additional success factors in (Marek et al, 2015;Patel, Pettitt, & Wilson, 2012;Tsanos et al, 2014;Yoon et al, 2017). However, the search missed five relevant papers of which we were aware: (Bedwell et al, 2012;De Feijter et al, 2018;Kolfschoten et al, 2010;Kotlarsky & Oshri, 2005;Lwakatare et al, 2015). We only found additional factors in Bedwell et al (2012).…”

Section: Towards a Framework Of Success Factors For Collaborationmentioning

confidence: 94%

“…Understanding and respect for each other and their respective organizations: how they operate, their cultural norms and values, limitations, and expectations (Kolfschoten et al, 2010;Mattessich & Monsey, 1992), confidence (Mohr & Spekman, 1994), professionals trust each other, respect (De Feijter et al, 2018;Tsanos et al, 2014) and human-related issues (Kotlarsky & Oshri, 2005). Conflict (Patel et al, 2012).…”

Section: Conflictmentioning

confidence: 99%

“…Representatives are included from each segment of the community who will be affected by its activities (De Feijter et al, 2018;Mattessich & Monsey, 1992). Team composition, skills, experience, psychological factors, wellbeing (Patel et al, 2012).…”

Section: -Appropriate Crosssection Of Membersmentioning

confidence: 99%

“…DevOps) appear to be especially relevant (Rodríguez et al, 2017). To aid in adopting DevOps (De Feijter, Overbeek, Van Vliet, Jagroep, & Brinkkemper, 2018) propose a DevOps competence model and a DevOps maturity model. However the case study was conducted in one organization, which poses a limitation on the generalizability of the case study results.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Success Factors of Collaboration in the Context of Devops

Belzen¹,

Kruijff

Trienekens³

2019

12th IADIS International Conference Information Systems 2019

View full text Add to dashboard Cite

Context: Collaboration is an important aspect of DevOps. However, researchers continue to report problems with collaboration between development and operations. Objective: We aim to contribute to a better understanding of collaboration in the context of DevOps, especially to aid in adopting DevOps. Method: We conducted a literature review on collaboration and corresponding success factors. For practice we classified the factors into factors influencing the likelihood of collaboration and factors influencing the performance of collaboration, to aid in the adoption of DevOps. We will validate the factors of collaboration in a DevOps context using an inductive approach, i.e. semi-structured interviews and document studies. Results: We developed an initial framework of success factors and classified the found success factors. Subsequently we conducted two interviews. We learned that most factors are considered as important, however few factors could be confirmed and no more factors are added. We will interview the other respondents to prove the applicability of the framework. Which may identify promising avenues for further development of the framework. Conclusions: This is study is not finalized yet, therefore we cannot fully answer the main research question.

show abstract

Section: Towards a Framework Of Success Factors For Collaborationmentioning

confidence: 94%

Section: Conflictmentioning

confidence: 99%

Section: -Appropriate Crosssection Of Membersmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Success Factors of Collaboration in the Context of Devops

Belzen¹,

Kruijff

Trienekens³

2019

12th IADIS International Conference Information Systems 2019

View full text Add to dashboard Cite

show abstract

“…Feijter DevOps maturity model [8], shown in Table-1, includes focus areas that enables software production organizations to mature in a fine grain manner. The model is dedicated to be used by software product organizations (SPO) that produces software to be used by several customers but not a customized software for specific customer.…”

Section: Feijter Maturity Modelmentioning

confidence: 99%

A Research on DevOps Maturity Models

Zarour*¹,

Alhammad²,

Alenezi³

et al. 2019

IJRTE

View full text Add to dashboard Cite

Despite the big number of software process models currently available which have been used and practiced for many years, we could not till now totally solve the problem of projects’ late submissions! Meanwhile Software have constantly become bigger, more complex, and require high quality. A recently developed model, called DevOps, aims at producing fast and high-quality releases by bringing the development and operation team to work together. Unfortunately, DevOps is still lacking a clear definition as well as empirical studies that document the experience in implementing and enhancing it. Maturity models are used as a tool to assess the effectiveness of an organizational processes on adopting certain practices and identify what capabilities they need to acquire next in order to improve their performance and reach higher maturity level. However, there are few DevOps maturity models which have been emerged as means to assess DevOps adopted practices. This research aims to identify and benchmark the DevOps maturity models available in literature. We were able to identify several maturity models and compare among them

show abstract

Assessing BizDevOps maturity using international standards: Case studies and lessons learned

Sanjurjo,

Pedreira,

García

et al. 2024

J Software Evolu Process

View full text Add to dashboard Cite

DevOps has emerged as a practical approach to the interaction between development and operations. This approach has been extended to the interaction with business functions, generating the term BizDevOps. Although many proposals and tools support BizDevOps from a technical viewpoint, there has been no significant improvement in management aspects, such as evaluating the practices and processes involved in the area. This paper presents two case studies on the assessment of BizDevOps practices using MMBDO (Maturity Model for BizDevOps), a maturity model for BizDevOps based on international ICT standards. The case studies were conducted in two organizations with different profiles: a large multinational ICT company with a unit specialized in providing DevOps to the rest of the company and a small software development company that implements DevOps practices as part of its development system. The evidence we obtained in the case studies supports the adequacy of MMBDO for assessing the maturity of BizDevOps in real companies. Also, the combination of the two case studies supports the adequacy of the model for being used in companies with different sizes and levels of maturity. MMBDO is an adequate proposal for assessing the maturity of BizDevOps in software organizations and a suitable tool for process improvement.

show abstract

DevOps Competences and Maturity for Software Producing Organizations

Cited by 25 publications

References 19 publications

Success Factors of Collaboration in the Context of Devops

Success Factors of Collaboration in the Context of Devops

A Research on DevOps Maturity Models

Assessing BizDevOps maturity using international standards: Case studies and lessons learned

Contact Info

Product

Resources

About