A Comparative Analysis of Agile Maturity Models

Leppänen, Mauri

doi:10.1007/978-1-4614-4951-5_27

Cited by 32 publications

(50 citation statements)

References 38 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It is a pity that researchers keep inventing new ones instead of validating (or even merging) existing tools to actually find a couple that works. Even the same year as the work of Leppänen (2013) was presented, more models have been suggested (by e.g. Soundararajan (2013)).…”

Section: Discussionmentioning

confidence: 99%

See 1 more Smart Citation

The prospects of a quantitative measurement of agility: A validation study on an agile maturity model

Gren

Torkar

Feldt

2015

Journal of Systems and Software

View full text Add to dashboard Cite

Agile Development has now become a well-known approach to collaboration in professional work life. Both researchers and practitioners want validated tools to measure agility. This study sets out to validate an agile maturity measurement model with statistical tests and empirical data. First, a pretest was conducted as a case study including a survey and focus group. Second, the main study was conducted with 45 employees from two SAP customers in the US. We used internal consistency (by a Cronbach's alpha) as the main measure for reliability and analyzed construct validity by exploratory principal factor analysis (PFA). The results suggest a new categorization of a subset of items existing in the tool and provides empirical support for these new groups of factors. However, we argue that more work is needed to reach the point where a maturity models with quantitative data can be said to validly measure agility, and even then, such a measurement still needs to include some deeper analysis with cultural and contextual items.

show abstract

Section: Discussionmentioning

confidence: 99%

“…The fact that the different agile maturity models have the same agile practice in a range of different levels (Leppänen, 2013), also indicates that the maturity levels of agility are not evident. Maybe this is a syndrome of not letting go of the control mechanisms that agile principles suggest should be more in the periphery.…”

Section: Discussionmentioning

confidence: 99%

The prospects of a quantitative measurement of agility: A validation study on an agile maturity model

Gren

Torkar

Feldt

2015

Journal of Systems and Software

View full text Add to dashboard Cite

show abstract

“…Therefore there appears to be a sound rationale to attempt to link agile practices to traditional maturity model. However as Meyer [47] also points out, this is in marked contrast to the general perception of agile advocates who view the two as incompatible and this has given rise to a substantial number of agile maturity models [44]. Fritzsche and Keil [23] attempted to determine which CMMi processes are supported by agile methods with some adjustments and which processes are in conflict.…”

Section: Agile Maturitymentioning

confidence: 92%

Agile Software Development – Adoption and Maturity: An Activity Theory Perspective

Chita

2018

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. This paper suggests that Activity Theory is a useful lens for examining aspects of agile software development adoption and maturity. Implementing agile approaches is influenced by many factors and attention is focused on individual and collective software development activity within an organisation's socially constructed environment. The research aim is to examine specific organisational, historical, cultural and social hindrances and facilitators that impact individual and collective learning opportunities and subsequent implementation of agile practices. This paper reports on the initial stages of research that consisted of a series of interviews and a survey. The results indicate that socially constructed hindrances and tensions are wide spread and vary in the levels at which they occur. They also correlate with many of the factors that influence agile maturity that have already been identified within the literature. This study contributes to research by integrating elements of learning theory and agile software development practice.

show abstract

“…Capability maturity model (CMM) and CMMI are the most well‐known maturity and assessment models in software development 34–36 . As widely recognized software process assessment framework, CMM for Software (SW‐CMM) provides software organizations with guidance on how to control of their processes for developing software and how to establish a strong culture of software engineering and management 37 .…”

Section: Research Backgroundmentioning

confidence: 99%

“…For this purpose, SW‐CMM introduces the basis for a process maturity assessment in terms of the five maturity levels: Level 1 (Initial), Level 2 (Repeatable), Level 3 (Defined), Level 4 (Managed), and Level 5 (Optimizing) as described in Table 1. Although agile principles are not visible in the structures and contents of CMM‐based models, some correspondences between agile principles and CMM levels have been recognized in literature; in most of the maturity models, the agile practices are positioned onto the maturity levels 34,38 …”

Section: Research Backgroundmentioning

confidence: 99%

Business process management approach for improving agile software process and agile maturity

Köse

2020

J Software Evolu Process

View full text Add to dashboard Cite

Continuous improvement of agile software processes is inevitable in order to reach sustainable and high‐quality project outcomes. In this sense, organizations need guidance on how to apply agile software process improvement effectively; comprehensive approaches with in‐depth analysis and guidelines are required to keep software processes in balance and to continuously improve them, as in a typical business process, over time. This research aims to explore the implementation of Business Process Management approach for improving an agile software process and accordingly agile maturity level. Many organizations utilize from Business Process Management approach in order to improve workflows and to discover organization‐specific weaknesses. For this purpose, the study presents a practical, flexible model based on Business Process Management approach for agile software process improvement, which also incorporates maturity assessment for measuring the agile maturity level. Furthermore, an exploratory case study with a triangulation methodology of mixed methods was carried out for implementation of the model. The research puts forward that Business Process Management approach can be used for in‐depth analysis of agile software process, discovery of problems, and redesign of the process. The research roadmap introduces worthwhile insights on agile software process improvement for researchers and practitioners.

show abstract

A Comparative Analysis of Agile Maturity Models

Cited by 32 publications

References 38 publications

The prospects of a quantitative measurement of agility: A validation study on an agile maturity model

The prospects of a quantitative measurement of agility: A validation study on an agile maturity model

Agile Software Development – Adoption and Maturity: An Activity Theory Perspective

Business process management approach for improving agile software process and agile maturity

Contact Info

Product

Resources

About