Expanding the concept of requirements traceability The role of electronic records management in gathering evidence of crucial communications and negotiations

Purpose – Despite its tremendous success and achievements, the information science (IS) industry has been plagued by shadows of failure and inefficiency since its early days. This paper takes the stance that poor communication with target organizations and users is one of the major causes of these problems. If this communication is not properly recorded and managed, many of the agreed decisions may never be assumed by target organizations, therefore leaving project managers entirely responsible for failures or deviation from initial requirements. Nonetheless, the vast majority of Software (SW) development companies have very weak provision for Electronic Records Management (ERM). This is evident from the persistent use of ISO 9001 and ISO 90003 in their Quality Assurance (QA) and the consistent neglecting of the ISO 15489 standard for records management. This paper aims to examine this issue

Design/methodology/approach – Since there are no studies in this area, this research employed an inductive qualitative research approach that consisted of a combination of critical literature review, an exploratory case study and thematic analysis.

Findings – This paper reports on the study of an SW company that implemented ERM policies and an in-house system that not only supports the recording of documentation and evidence for every phase of the development, but also the very difficult processes of organizational learning.

Practical implications – This paper is of interest to both IS academics and practitioners, namely those interested in QA and ERM.

Originality/value – There is very little research in this area that can inform both academics and practitioners on how to use ERM within SW project management practices. This paper aims at providing early insights into ways of addressing this gap and at generating discussion in this area.