Diagrams or structural lists in software project retrospectives - An experimental comparison

dc.contributorAalto-yliopistofi
dc.contributorAalto Universityen
dc.contributor.authorLehtinen, Timo O.A.
dc.contributor.authorMäntylä, Mika V.
dc.contributor.authorItkonen, Juha
dc.contributor.authorVanhanen, Jari
dc.contributor.departmentDepartment of Computer Science
dc.date.accessioned2017-05-11T07:14:33Z
dc.date.available2017-05-11T07:14:33Z
dc.date.issued2015
dc.descriptionVK: Lassenius, C.
dc.description.abstractRoot cause analysis (RCA) is a recommended practice in retrospectives and cause–effect diagram (CED) is a commonly recommended technique for RCA. Our objective is to evaluate whether CED improves the outcome and perceived utility of RCA. We conducted a controlled experiment with 11 student software project teams by using a single factor paired design resulting in a total of 22 experimental units. Two visualization techniques of underlying causes were compared: CED and a structural list of causes. We used the output of RCA, questionnaires, and group interviews to compare the two techniques. In our results, CED increased the total number of detected causes. CED also increased the links between causes, thus, suggesting more structured analysis of problems. Furthermore, the participants perceived that CED improved organizing and outlining the detected causes. The implication of our results is that using CED in the RCA of retrospectives is recommended, yet, not mandatory as the groups also performed well with the structural list. In addition to increased number of detected causes, CED is visually more attractive and preferred by retrospective participants, even though it is somewhat harder to read and requires specific software tools.en
dc.description.versionPeer revieweden
dc.format.extent17-35
dc.format.mimetypeapplication/pdf
dc.identifier.citationLehtinen , T O A , Mäntylä , M V , Itkonen , J & Vanhanen , J 2015 , ' Diagrams or structural lists in software project retrospectives - An experimental comparison ' , Journal of Systems and Software , vol. 103 , pp. 17-35 . https://doi.org/10.1016/j.jss.2015.01.020en
dc.identifier.doi10.1016/j.jss.2015.01.020
dc.identifier.issn0164-1212
dc.identifier.issn1873-1228
dc.identifier.otherPURE UUID: 4f63bd9e-c261-4c96-af34-3888135c4914
dc.identifier.otherPURE ITEMURL: https://research.aalto.fi/en/publications/4f63bd9e-c261-4c96-af34-3888135c4914
dc.identifier.otherPURE LINK: http://dx.doi.org./10.1016/j.jss.2015.01.020
dc.identifier.otherPURE FILEURL: https://research.aalto.fi/files/11693847/1_s2.0_S0164121215000151_main.pdf
dc.identifier.urihttps://aaltodoc.aalto.fi/handle/123456789/25504
dc.identifier.urnURN:NBN:fi:aalto-201705113888
dc.language.isoenen
dc.relation.ispartofseriesJOURNAL OF SYSTEMS AND SOFTWAREen
dc.relation.ispartofseriesVolume 103en
dc.rightsopenAccessen
dc.subject.keywordcause effect diagram
dc.subject.keywordcontrolled experiment
dc.subject.keywordpost mortem analysis
dc.subject.keywordretrospective
dc.subject.keywordroot cause analysis
dc.subject.keywordcause-effect diagram
dc.titleDiagrams or structural lists in software project retrospectives - An experimental comparisonen
dc.typeA1 Alkuperäisartikkeli tieteellisessä aikakauslehdessäfi
dc.type.versionpublishedVersion
Files