Teaching Action Research
Miroslaw Staron
TL;DR
The chapter argues that software engineering faces a crisis of limited empirical results and poor transfer to practice. It presents action research as a collaborative, cyclic methodology that embeds researchers within host organizations to plan, intervene, and evaluate changes, generating knowledge across process, organizational, tooling, and artefact dimensions. Key contributions include a clear articulation of the pillars (host embedding, interventions, and action teams), a five-phase cycle, governance roles (action team, reference group, management), and comprehensive guidance on ethics and pedagogy. The work highlights practical implications for industry-academia collaboration and offers teaching guidelines and concrete examples to facilitate adoption and effective teaching of action research in software engineering.
Abstract
Action research entered into software engineering as one of the responses to the software engineering research crisis at the end of the last millennium. As one of the challenges in the crisis was the lack of empirical results and the transfer of research results into practices, action research could address these challenges. It is a methodology where collaboration and host organizations are the focus of knowledge discovery, development, and documentation. Although the method is often well received in industrial contexts, it isn't easy to learn as it requires experience and varies from organization to organization. This chapter describes the pillars of action research as a methodology and how to teach them. The chapter includes examples of teaching action research at the bachelor, master, and PhD levels. In addition to theory, the chapter contains examples from practice.
