A Requirement Constraint Impact on Project Development Life Cycle

Running head: A REQUIREMENT CONSTRAINT IMPACT ON PROJECT DEVELOPMENT LIFE
CYCLE
A REQUIREMENT CONSTRAINT IMPACT ON PROJECT DEVELOPMENT LIFE
CYCLE
Name of the Student
Name of the University
Author Note

1A REQUIREMENT CONSTRAINT IMPACT ON PROJECT DEVELOPMENT LIFE CYCLE
Identified Constraint
Projects are undertaken the to improve the capability of a firm or to mitigate a
problem that is existing [1]. Hence, it becomes of great prominence that proper attention is
provided to it so that the outcome will improve the subject or scenario. One of the major
obstacles in the way of a successful project is the project constraints. Hence, the discussed
section is dedicated at discussing the constraints that had been identified. The identified
constraints will assist in determination of the impact and how they can be mitigated.
Waterfall Style Project
The discussed system development method is one of the most prominently used
system development methodology which offers a well-defined structure of the work to be
undertaken for the successful delivery of the project [2]. However, the discussed
methodology is faced by certain constraints those impact the output of the project delivery.

2A REQUIREMENT CONSTRAINT IMPACT ON PROJECT DEVELOPMENT LIFE CYCLE
Scope
According to Kramer (2018), the most prominent challenges that are offered by the
waterfall model includes its unpreparedness for changes and so it ignores changes; it does not
consider end users and client as part of the development phase; and finally, it delays testing
until the completion. Other challenges are also offered by the discussed model however, the
three discussed above leads to compromising of the scope of the project. The ignoring of the
client and user feedbacks along with failure of inducting changes during the development
phase and delayed testing offers inferior quality of deliverable [4]. The inferior quality output
compromise the scope of the project and is not satisfying for the client, users or even the
developers.
Scope of the project is one of the most crucial aspect of a project and it mainly
depends upon three factors. Planning, controlling and closing [5]. In case of the waterfall
model the project is well planned as proper scheduling and budgeting is done before initiation
of the system development life cycle. However, the controlling of a project focuses on scope
creep, approval or disapproval of changes along with other factors. However, as the discussed
methodology does not favour the idea of inducting changes that are not part of the initial plan
it leads to failure of the controlling process thus impacting the scope [4]. The closing process
includes auditing of the deliverables and assessment of the original plan and it is included as
part of the model.
Hence, to summarise it would be justified to state that due to lack of proper
assessment of the controlling process the discussed methodology compromises on the scope
of the project.