Managing Risk in Software Process Improvement: An Action Research Approach

By J. Iversen, Lars Mathiassen, P. Nielsen. MIS Q., 2004

309 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Guidelines for conducting and reporting case study research in software engineering (2009, methodology): “In software process improvement (Dittrich et al. 2008; Iversen et al. 2004) and technology transfer studies (Gorschek et al.”
Experimentation in Software Engineering (2012, methodology): “In software process improvement [44, 85] and technology transfer studies [66], the research method could be characterized as action research if the researcher actively participates in the improvements.”
Co-Creation in Virtual Worlds: The Design of the User Experience (2011, background): “Action research is a collaborative, rigorous, iterative process that goes through several phases in several cycles (Baskerville and Wood-Harper 1998; Davison et al. 2004; Iversen et al. 2004).”
Being Proactive: Where Action Research Meets Design Research (2005, unknown): “The criteria for DR are applied below to the AR exemplar of Iverson et al. (2004). The research was part of a larger research program and the specific aim of the project was to improve the implementation of software process initiative (SPI) practices.”
Action Research is Similar to Design Science (2007, methodology): “Iversen et al., (2004) is study is not the typical action research (Jarvinen 2004a, Section 5.3) but more close to the field test (Jarvinen 2004a, Section 3.2) of the frameworks and methodologies the researchers developed based on their literature survey.”