A Strategy for Managing Apathetic Users During Requirements Definition

Abstract

Requirement elicitation is the most important software development activity that determines the success of a software development project, and the quality of a software product is highly dependent on the correctness, completeness and conciseness of the outcome of this phase. Users play a key role in this process and the associated outcome which makes it imperative to involve them throughout this phase. Different categories of users were identified during a requirements elicitation activity, as input from all the groups was required to gather adequate requirements that was representative of the users’ needs. There is the risk of poor requirements gathering if any category of users shows apathy or lack of interest in expressing their needs regarding a software product. Participants for this study was derived using purposive sampling. A qualitative approach was adopted, comprising a semi-structured interview with key informants, after an informal interactive session with them to educate and acquaint them with their significant role in the success of the project. This paper reports the risk management strategy adopted in the management of these apathetic users during requirements definition process to ensure they made the needed contribution and elicited their needs. This intervention helped to obtain requirements from all categories of users of the intended software product. The resulting software product was well accepted and used by all because their needs were captured and incorporated in its development.