Scope Creep: Definition, Controls, Ways to Avoid and Advantages

This article discusses the definition of scope creep, controls to manage it, ways to avoid it, and its advantages. It also provides examples of scope creep and how it can affect a project. The article emphasizes the importance of clear communication between clients and developers to prevent scope creep. It also highlights the benefits of scope creep in certain situations.

Running head: SCOPE CREEP
SCOPE CREEP
Name of the Students:
Name of the University:
Author Note:

1
SCOPE CREEP
Scope creep definition
Scope creep refers to the situation where, additional requirements from the clients can
make the expansion of the project (Sarosa and Tatnall 2015). In most cases the requirements
provided in the scope creep are not pre defined in the initial requirement stage of the project.
An example can define the situation of scope creep clearly. In a project of developing the
online ticket booing system certain requirements are provided by the clients to the developers.
The clients can add more specification like – adding extra link for the time checking or changing
the view a certain user view of the ticket. These modifications are not a part of initial
requirements, but the developers have to work on those modifications as per the requirement of
the client.
Sometimes the scope creep can occur in case of choosing technologies also. The
developers can realize the usefulness of a new technology in the middle of developing a project
using certain technology (Janssen, Van Der and van Veenstra 2015). In this case the changes are
made accordingly.
Controls in the project to manage the scope creep:
In the railway reservation system development, the scope creep was to change the user
vie of the ticket. This task was manageable, which means the developers can modify the code to
change the user view of the ticket.
The addition of the extra link for time checking was not possible at that stage of the
project as that modification can lead to change the major structural change of the whole project.

2
SCOPE CREEP
Ways to avoid the scope creep:
In order to avoid the scope creep the requirements should be clear from the client’s side,
whereas the developers should understand the requirements clearly (Snyder 2014). In this case,
the clear understanding between the client and the developers about the requirements are needed
to be done.
Determination of the technique for handling the change of control is also useful for the
prevention of scope creep. The identification of the types of changes that can be possible to make
are needed to be evaluated in the beginning of the project.
Advantages of scope creep:
Sometimes the scope creep can help to improvise the project (Madhuri, Suma and
Mokashi 2018). In case of railway reservation system the changing of the view of ticket helps to
present the product in a more proper way. The addition of the extra link for time checking can
improvise the project. However, that can not be done due to the technical reason.
Sometimes scope creep enables the option of considering the use of new technologies in
the development.

3
SCOPE CREEP
References
Janssen, M., Van Der Voort, H. and van Veenstra, A.F., 2015. Failure of large transformation
projects from the viewpoint of complex adaptive systems: Management principles for dealing
with project dynamics. Information Systems Frontiers, 17(1), pp.15-29.
Madhuri, K.L., Suma, V. and Mokashi, U.M., 2018. A triangular perception of scope creep
influencing the project success. International Journal of Business Information Systems, 27(1),
pp.69-85.
Sarosa, S. and Tatnall, A., 2015. Failure to launch: Scope creep and other causes of failure from
an actor-network theory perspective. International Journal of Actor-Network Theory and
Technological Innovation (IJANTTI), 7(4), pp.1-13.
Snyder, C.S., 2014. A guide to the project management body of knowledge: PMBOK (®)
guide. Project Management Institute: Newtown Square, PA, USA.