Project Management Methodologies: Comparing Agile and Waterfall SDLC

This essay provides a detailed analysis of project management methodologies, focusing on a comparison between the Waterfall and Agile models. It defines project management methodologies and their role in streamlining project activities, highlighting the importance of methodologies in addressing project-related challenges. The essay discusses specific methodologies such as PMBOK, PRINCE2, and SDLC, with a particular emphasis on contrasting the Waterfall and Agile approaches. The Waterfall model is presented as a structured, sequential method, while Agile is characterized by its iterative and flexible nature. The essay also explores the relationship between these methodologies and the project life cycle, emphasizing Agile's adaptability to changing requirements and Waterfall's focus on logical progression and thorough planning. Desklib offers students access to this essay and a wealth of other solved assignments and study resources.

Running head: PROJECT MANAGEMENT
Project Management
Name of the Student
Name of the University
Author Note

1PROJECT MANAGEMENT
Methodology Definition:
Methodology of a project management can be said as the systematic and theoretical
analysis of the various kind of project management methods that can be applied in a
particular part of the study. Theoretical analysis is also defined by this study in the different
principles and the methods which is associated with a particular knowledge branch (Janssens,
2018). The main objective of the methodologies is to solve the problems associate with the
activities of the project management like task methods, phases, techniques and tools. The
methodologies are used in different areas of the computer science to deal with the particular
discipline question (Stoica, Mircea & Ghilic-Micu 2013).
Role of methodology:
The main goal of the methodologies is to complete the tasks that are required and
important for the designing of the project quickly. The problems and the risks that will
generate with the project will be required handling properly for the successful project
management. Throughout the project life cycle the methodologies of the project management
is used in the project (Vijayasarathy & Butler 2016). The whole methodology is divided into
many stages and each of the stage has its own significant role for the project success. Each
stage meet its target to complete the project efficiently. The methodologies enable the
procedure to tackle the various project in an integrated and systematic manner. Using the
methodology in the project management provide many benefits to the project. The strategic,
tactical and the operational level of the project improves because of using the methodology
(Mesjasz, 2016).
Project Management Methodologies:
Project Management Body of Knowledge (PMBOK):

2PROJECT MANAGEMENT
The project management body of knowledge is defined as the set of various
different terminology and standard guidelines which will be used in the project
management. This can be also termed as the collection of various completed
processes, guidelines, terminologies which would be granted as the industry standards
of the project management.
PRINCE2:
The term PRINCE stands for Projects IN Controlled Environments. The
PRINCE2 is a method which is structured for the project management and for the
certification of program of the people who is practicing. This method focusses on the
project deviation into manageable and controllable stages.
SDLC:
SDLC stands for Software Development Life Cycle. The SDLC is mainly used
by the industry of software for the design purpose and for testing and development.
This life cycle is needed to be completed properly for getting the software of high
quality.
Waterfall:
Waterfall is a software development model use to develop a software.
Waterfall follows a sequential linear design that is based on the engineering design. In
the waterfall model, the development can only go through the next stage if the
previous stage is completed.
Agile:
Agile is a practice method of continuous iteration of the development
processes and the testing part of the SDLC in the project. In the agile methodology,

3PROJECT MANAGEMENT
development and the testing activities are not like the waterfall model as the processes
are done simultaneously.
Comparison between Waterfall and Agile Methodology:
In the phase of the development in waterfall model total phase is divided in to several
phases. The agile methodology is able propose the development segregation of the project life
cycle.
The Differences between Waterfall Model and Agile Model:
The waterfall model is a structured methodology of the software development, which
is rigid. The agile methodology provides an approach that is flexible.
Relation of the Chosen Methodologies to the Project Life Cycle (PLC):
The agile methodology do not us the sequential development process as it uses the
iterative process. Day by day the requirements are changing, so the approach that are flexible
is the required for the project (Kerzner & Kerzne,r 2017). In the agile approach the new
changes is constantly applied in the project in form of new technology. This allows the teams
of the software development to divide the whole processes into many segments and then test
the all segments. This will enable the quick delivery of the project.
The waterfall model is mainly focus on the different steps logical progression
throughout the entire project life cycle. The developer is only moved to the next step after
completing the previous step successfully (Joslin & Müller 2015). So there will be no error in
the project. So it is necessary that the plan is made properly in the initiation phase.

4PROJECT MANAGEMENT
Reference:
Janssens, J. (2018). Project and Portfolio Maturity for Waterfall and Agile: Convergence of
Layered Needs in Different Ecosystems. In Developing Organizational Maturity for
Effective Project Management (pp. 253-277). IGI Global.
Joslin, R., & Müller, R. (2015). Relationships between a project management methodology
and project success in different project governance contexts. International Journal of
Project Management, 33(6), 1377-1392.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Mesjasz, C., Bartusik, K., Malkus, T., & Wo, K. (2016). Complexity and design of
management systems.
Stoica, M., Mircea, M., & Ghilic-Micu, B. (2013). Software Development: Agile vs.
Traditional. Informatica Economica, 17(4).
Vijayasarathy, L. R., & Butler, C. W. (2016). Choice of software development
methodologies: Do organizational, project, and team characteristics matter?. IEEE
software, 33(5), 86-94.

5PROJECT MANAGEMENT