Two case studies to explore pros/cons and to assess applicability of Nexus maturity model

Abstract

Nexus maturity model, which is created as a structured gradual guideline for the companies wishing to adopt Nexus framework, is a new model, so the main purpose of this paper is to assess the model. Moreover, to explore pros and cons of the model to enlighten the researchers and implementers in the industry is aimed. Two case studies were conducted to collect data and to test three hypotheses. The second case study was executed 4 months later than the first case study which was completed with the same Nexus team members at the same company. During the case studies, structured interview technique was used via face-to-face meetings. Firstly, the results of the case studies show that this model can be applied easily by using the metrics to measure the success percentages of Nexus practices. Secondly, the practices with the low achievement percentage can be determined, the improvement strategies can be defined by means of the goals, objectives, practices of the model and investigation of the reasons as well. Lastly, with application of the improvement strategies, Nexus adoption success can be improved for higher levels by tracking Nexus maturity model elements. This paper presents the first application of Nexus maturity model in the industry, and also the first study to assess the model with its pros and cons in the literature.

A longitudinal case study on Nexus transformation: Impact on productivity, quality, and motivation

“…Bittner et al 16 described the details of these components and provided guidelines for an effective implementation of Nexus in their book. In another study, Firat et al 17 proposed a five‐step approach to guide companies, who want to adopt the Nexus framework. They also introduced a maturity model for evaluation.…”

“…The first guide for Nexus 15 was published in 2015, and its adoption is not very common in large-scale organizations yet. Accordingly, there are only a few studiess 16,17 published in the literature on Nexus. We previously published an experience report 18 on the adoption of Nexus for the development of a product, which has been previously developed with Scrum.…”