Symptom‐based improvement recommendations

For this paper, we have identified a list of 32 characteristic symptoms that is often discussed during assessments, generated by two experienced assessors who had undertaken maturity assessments in more than 300 companies. We then use cognitive mapping and the “five whys” technique to look beyond th...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:Journal of software : evolution and process 2023-08, Vol.35 (8), p.n/a
Hauptverfasser: Pries‐Heje, Jan, Johansen, Jørn, Korsaa, Morten
Format: Artikel
Sprache:eng
Schlagworte:
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
Beschreibung
Zusammenfassung:For this paper, we have identified a list of 32 characteristic symptoms that is often discussed during assessments, generated by two experienced assessors who had undertaken maturity assessments in more than 300 companies. We then use cognitive mapping and the “five whys” technique to look beyond the symptoms and reveal the underlying problems or causes of the problems. Following that, we evaluate our findings through the design and evaluation of a web‐based tool where users can score statements based on a formulation of the symptoms. This enables us to recommend to users the areas where they probably need to improve. We designed the tool in three learning cycles of design evaluation and ended up in a summative evaluation where we compared the outcome of using the website tool with a CMMI maturity assessment. We conclude that a systematic quest for symptoms coupled with scoring statements based on the symptoms can point to improvement areas. However, we conclude that doing so is no substitute for a maturity assessment; the scoring of statements cannot reveal the maturity of the organization, but it can quickly and easily point in a useful direction and provide recommendations for going in that direction. Analyzing the symptoms described by the participants in maturity assessments with “five times why” reveals a pattern that can be used to provide improvement recommendations without a formal assessment.
ISSN:2047-7473
2047-7481
DOI:10.1002/smr.2375