Demonstrating the elaborated action design research (eADR) model to address communication challenges during software development

Abstract

Communication is a powerful, universal, everyday activity that impacts many, if not all, aspects of our lives. The importance and complexities of communication are however still often overlooked. Inadequate communication during software development projects at a medium-sized enterprise, Company-GIS (CGIS), caused delays in project tasks, negatively impacting quality, on-time delivery, and delivery within budget. In this study, we argue that a collaborative methodology was required to ensure adequate diagnosis of the problem, creating multiple artefacts to address the communication problems. We argue that a recent research methodology called action design research (ADR) is best suited for a practice-inspired problem. Acknowledging the latest developments within the ADR discipline, we believe that the elaborated action design research (eADR) process model addressed the need to explicitly show our knowledge contributions in the form of two artefacts: (1) An Agile requirement engineering solution (ARES) to address the communication problems, the primary artefact; and (2) A taxonomy of perceived communication problems, a secondary artefact. In this experience report, we indicate that the eADR process model was instrumental in facilitating diagnosis, followed by design, implementation, and evolution of the primary artefact, the ARES. The practical demonstration of ARES also highlighted the need for further evolution of the eADR as a method artefact. Based on our reflections on applying the eADR, we suggest changes to the eADR including an additional design cycle phase, suggestion, between problem formulation and artefact creation, as well as merging reflection and learning into a single phase.