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

Abstract

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.

A “No-Code” App Design Platform for Mobile Health Research: Development and Usability Study

“…Several strategies have been proposed to prevent scope creep in software development [42]. For example, mapping the impact of a change as a percentage of the time, cost, and quality of the product could help an agile project manager decide whether to accept or reject the change.…”

Normalizing White-Collar Wrongdoing in Professional Service Firms

“…There are many ways scope creep may occur in project-based work, including schedule constraints, poor scope management, requirement volatility (Aizaz et al 2021;Ajmal et al 2020;Komal et al 2020).…”

Exploring Aspects of Agile Software Development Risk – Results from a MLR

“…In a systematic literature review published in July 2021, the primary factors causing scope creep within an agile software development team were identified. The diagram below highlights these factors, with the percentage referring to the frequency of occurrence within agile teams according to project managers surveyed as part of the SLR [10]. The three most frequent factors will be further detailed in Fig.…”

“…In this case, ego refers primarily to the behavior and personality of the project manager, who may have "inflated pride, ego, or confidence" in either themselves or their teams [10]. As a result of this, they may be more willing to accept new requirements and features that are beyond the capacity of the development team.…”

“…Agile development may be primarily suited to small to medium project sizes due to its prioritisation of "fast development and fast delivery" [10], though innovations such as SAFe [41] may aid agile in larger settings. The requirements of frequent, incremental deliverables and real-time communication become harder to achieve with larger projects, as communication (e.g.…”