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.
Highlights
Over the years, the success of project management has been measured using the three metrics; time, cost and quality called as ‘‘iron triangle’’ or ‘‘triple constraint’’
RESEARCH METHOD The purpose of this research is to extend our prior research to develop a hierarchical framework of scope definition elements and to distinguish cause and effect elements by 1) identifying the software projects scope definition aspects from 2016 to 2020, 2) deriving interrelationships among the aspects, 3) classifying the aspects according to their influencing and dependence degree, 4) determining the intensity of cause-and-effect relationships among the elements
FRAMEWORK DEVELOPMENT USING Interpretive Structural Modeling (ISM) PROCESS–INTERRELATIONSHIPS OF ELEMENTS Using ISM methodology, this study aims to build a framework of software scope elements to better understand their
Summary
The success of project management has been measured using the three metrics; time, cost and quality called as ‘‘iron triangle’’ or ‘‘triple constraint’’. While a project is considered to be successful if it satisfies the criteria of on-time, within budget, and according to the scope [1]. Software Project Management (SPM), a subdiscipline of project management plays a significant role in the development and successful completion of software projects. It involves the following activities: project planning, scheduling, budgeting, and risk analysis, etc. Project planning, which entails all the information about the project, concerning project deliverables, time, cost, communication, resources, etc., is believed to be a major contributor to the.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
