No abstract

Software project scope definition is complicated due to the diversity and magnitude of the information needed. An inadequate scope definition often results in project failure as it continues to emerge as the major cause of delays, changes/rework, and cost and schedule overruns. Literature mentions different tools and methods to verify, quantify, and control software scope definition. However, none of these methods and tools help in defining a complete scope. Since a well-defined scope in the early stages is a core ingredient for project success, therefore, previously we developed a method that includes 45 elements of the software project scope definition. Although these elements are noteworthy for project scope, some may influence others; and should be concentrated on more when defining the scope of the software projects. The objective of this present study is that it builds on our previous research and uses Interpretive Structural Modeling (ISM) to extract the interrelationships among the elements and Decision Making Trial and Evaluation Laboratory (DEMATEL) to determine the intensity of these relationships. Experts from academia and the software development industry were consulted to identify the relationships among the elements. ISM-DEMATEL approach indicates that the project manager's competence is the main driver. Further, requirements, stakeholders' expectations, cost estimates, project schedule, resource estimation, project summary, communication, consultation, top management support are among the most influential elements that are critical to focus on. Moreover, the findings of the study provide project managers with a better understanding of the elements and their interconnections thus, helping in achieving a better scope definition.INDEX TERMS Interpretive structural modeling (ISM), decision making trial and evaluation laboratory (DEMATEL), scope definition, scope elements, scope management, software projects.