How to assign cost to &amp;#x201C;avoidable requirements creep&amp;#x201D;: A step towards the waterfall's agilization

Puhl, Stefan; Fahney, Ralf

doi:10.1109/re.2011.6051623

Cited by 7 publications

(5 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The author has proposed a conceptual model for managers after taking interviews. The effect of the project scope is studied in various studies, and it is found that scope is as important as any other factor [27] [28] [29] [30]. Scope creep to be carried out in an adequately controlled way to overcome failure chances [26].…”

Section: Rq2 What Are the Current State-of-the-art Models Useful In Managing Scope Creep In The Agsd Context?mentioning

confidence: 99%

An Empirical Investigation of Factors Causing Scope Creep in Agile Global Software Development Context: A Conceptual Model for Project Managers

Aizaz

Khan

et al. 2021

IEEE Access

View full text Add to dashboard Cite

Scope creep is considered one of the crucial reasons for the failure of traditional software development projects. The ability to manage and control the change elements on a project, particularly the project scope, is a key to project success. The notion of the agile process was introduced to tackle the scope change-related challenges such as scope creep. By adopting an agile-footed process, the development organizations can react to the consistent market changes and client requests. However, continuous change accommodation may negatively impact the success of the targeted project since the project manager mainly focuses on controlling scope change rather than analyzing its impact on the cost and quality. The agileprocess advocates have accepted that this situation could happen even following agile methodology, which prompts compromising the quality, postponed plans, increment cost, plan to modify, and diminished consumer loyalty. Additionally, the scope-related challenge significantly increases, especially when managing scope creep in the global software development (GSD) context. Thus, there is a need to focus on scope creep factors in the context of AGSD. Motivated by this, current work aims at identifying the factors causing scope creep in the context of AGSD. To achieve the targeted objectives, we reported the current state-of-the-art related to existing scope creep models of AGSD. We adopted SLR and empirical study to address the formulated research questions. The current study also identifies the additional challenges of scope creep from the industrial perspective. Based on the obtained results, the current work proposes a conceptual model for scope creep to assist the agile practitioners to effectively handle the scope creep, which increases the project success and forecast change control effect on a software project. Moreover, the proposed conceptual model's effectiveness is validated through expert judgment and a case study. The obtained promising results ensure the additional aspects of AGSD; hence, we could overcome the project's overall risk by implementing the proposed model.

show abstract

Section: Rq2 What Are the Current State-of-the-art Models Useful In Managing Scope Creep In The Agsd Context?mentioning

confidence: 99%

An Empirical Investigation of Factors Causing Scope Creep in Agile Global Software Development Context: A Conceptual Model for Project Managers

Aizaz

Khan

et al. 2021

IEEE Access

View full text Add to dashboard Cite

show abstract

“…The quantitative research method is defined as "the systematic investigation of phenomena by gathering quantifiable data and performing statistical, mathematical or computational techniques" [74]. The results obtained from the quantitative analysis are considered reliable and objective by the majority of the experts and researchers [75].…”

Section: ) Sample and Data Collectionmentioning

confidence: 99%

The Impact of Scope Creep on Project Success: An Empirical Investigation

et al. 2020

View full text Add to dashboard Cite

Advocates of software engineering and software project management stated in the literature that creeping of scope is one of the most common causes for the failure of software projects. Also, advocates believed that it could occur in almost every software project, which leads to compromise in quality, delayed schedules, increase cost and decreased customer satisfaction. However, the lack of empirical evidence demands a comprehensive investigation to identify the factors of scope creep and to propose a conceptual framework to empirically evaluate the impact of scope creep on software project success. To determine the scope creep factors in this study, two exploratory methods, i.e. a Systematic Literature Review (SLR) and interview from experts are performed. Following the analysis of these methods, a conceptual framework is proposed. To empirically evaluate the proposed conceptual framework, data is collected through a survey method. Next, the collected data is analyzed through Partial Least Squares' Structural Equation Modelling (PLS-SEM). From the results, it is evident that the identified factors of scope creep are negatively associated with software project success. The results of empirical evaluation also second the findings of SLR. The outcome of the study may help the practitioners to understand the dynamics of factors, which undermine scope creep in software SMEs and to assist them in the development of effective control and mitigation strategies, therefore, to increase the project success rate. INDEX TERMS Scope management, scope creep, requirement creep, software project success, partial least squares structural equation modeling.

show abstract

“…Occurrences in research articles ef1-Project Priority [6], [7], [51], [77] ef2-Lack of Motivation and Direction [14], [18], [19], [66], [67], [78] ef3-Change Cost [5], [7], [8], [10], [18], [19], [47], [49], [50], [66], [69], [70], [71], [72], [74], [77], [79], [82], [83], [84], [85] ef4-Project Resources [7], [10], [67], [71], [86], [74], [80], [83], [72] ef5-Project Risks [7], [9], [10], [50], [66], [70], [77] ef6-Rework [7], [14], [19],…”

Section: Effectsmentioning

confidence: 99%

Measuring the Impact of Scope Changes on Project Plan Using EVM

et al. 2020

View full text Add to dashboard Cite

Earned Value Management (EVM) measures project performance against a baseline plan. It identifies deviations in budget and schedule, aids project managers in taking earlier corrective actions against cost and schedule overruns. Although the literature highlights the significance of scope by adopting it as a leading indicator to measure project success or failure. However, EVM does not include scope when evaluating the performance of any software project. While considering the importance of scope and its ever-changing nature, it is imperative to measure the effect of changes in scope on the project plan. To analyse such effects, this study aims to enhance the traditional EVM by incorporating scope into it. The main objectives of this paper are: i) to extract the effects of project scope changes, ii) to map extracted effects of project scope changes with Software Project Scope Rating Index (SPSRI) elements, and iii) to quantify the extracted effects and integrate them with EVM. An extensive literature review is conducted to achieve the first objective, which results in the seventeen unique effects; that were used to map with SPSRI elements. To forecast the variations in scope for a given project budget, Monte Carlo simulations were run on the top eight scope elements, whereas, the results were incorporated with EVM to identify the deviations between actual and projected values of scope's score and cost. Finally, the multivariate regression model was used to evaluate the influence of individual element on the overall estimated cost of the project. The correlation between the independent variables (SPSRI elements) and the dependent variable (overall cost) was calculated along with the valuation of each independent variable on the dependent variable. Moreover, the effects are statistically shown that independent variables have influenced the dependent variable. This technique could assist the project managers to forecast deviations in project scope earlier.

show abstract

How to assign cost to “avoidable requirements creep”: A step towards the waterfall's agilization

Cited by 7 publications

References 3 publications

An Empirical Investigation of Factors Causing Scope Creep in Agile Global Software Development Context: A Conceptual Model for Project Managers

An Empirical Investigation of Factors Causing Scope Creep in Agile Global Software Development Context: A Conceptual Model for Project Managers

The Impact of Scope Creep on Project Success: An Empirical Investigation

Measuring the Impact of Scope Changes on Project Plan Using EVM

Contact Info

Product

Resources

About