Managing Scope Creeps in Product Led Software-Based Organizations

Abstract

Scope creep presents a significant challenge for project managers throughout the project lifecycle. It can lead to budget overruns and schedule delays. This paper explores how project managers, especially those in software development organizations can effectively manage and prevent scope creep during project execution. It delves into the various factors that can contribute to changes in a project's scope and the resulting impacts. Historically, project management has placed more emphasis on cost, time, and performance, with less attention given to scope change management. This paper presents multiple solutions for addressing scope creep. One proposed solution involves establishing a contract to freeze the project's scope during the planning phase. While this approach effectively prevents scope changes, it may not be feasible for many projects. Another suggestion, put forth by T.J. Jach and J.R. Coat in their work "Managing the Change Process on Projects: A Step-by-Step Guide," is to incorporate "escape clauses" into project plans. These clauses involve predetermined procedures and utilize cost- benefit analysis to determine when and if a scope change is necessary. This method offers a structured approach for evaluating the potential impacts of scope changes and can be quite effective. (Jayalath & Somarathna, 2021) Keyword: Scope Creep, Customer Satisfaction, Perception, Expectations, Uncertainty, Security, Software, Expectations