A study on project scope as a requirements elicitation issue

Project scoping of features and functionalities required to meet the system objectives is critical for project success. An accurate determination of the system boundary to develop software has long been identified as a challenge that practitioners have been attempting to overcome. It is, therefore, important to understand the causes along with the consequences of poor project scope. This study presents the findings pertaining to project scope that influence the requirements elicitation activity and thereby impact the overall requirements engineering process. The causes that lead to such scope issues and related consequences are summarized. The challenges encountered due to poor scope are depicted using a cause-and-effect diagram. This study provides guidance that can assist practitioners to identify areas for improvements in determining project scope and that which can have a positive influence on the overall requirements elicitation process.