Project Management Methodologies: Agile vs Waterfall Models

This report provides a comprehensive overview of project management methodologies, defining methodology and its role in project management. It explores various methodologies like PMBOK, PRINCE2, SDLC, Waterfall, and Agile. The report compares Agile and Waterfall models, highlighting their similarities and differences. Furthermore, it examines the relationship of the chosen methodologies to the Project Life Cycle (PLC), emphasizing the iterative nature of Agile and the sequential approach of Waterfall. The report concludes by underscoring the importance of selecting appropriate methodologies for effective project management, referencing key literature to support the analysis and comparison of the models.

Running head: PROJECT MANAGEMENT METHODOLOGIES
Project Management Methodologies
Name of the Student
Name of the University
Author’s note

1PROJECT MANAGEMENT METHODOLOGIES
1. (a) Definition of Methodology
A project management methodology could be defined as the theoretical and
systematic analysis of the different kind of methods that would be applied to a particular field
of study. The methodology also defines about the theoretical analysis of the various body of
principles and methods that would be associated with a particular branch of knowledge
(Kerzner & Kerzner, 2017). The methodology normally serves as a guideline for the solving
of a particular problem with specific components such as tasks, phases, methods, tools and
techniques. The researchers of Computer Science make use of several methodologies in order
to deal with the questions within the particular discipline.
(b) Role of Methodology in Project Management
The primary aim of the use of different methodologies is to complete the important
tasks that would be required for the faster design of the project. Proper strategies would also
be required for the faster handling of the problems that would arise. The use of proper form
of methodology would be able to guide throughout the progress of the project. It also
provides different steps that should be followed and targets should be met from the starting of
the project to the completion of the project. The methodology would be helpful in enabling to
tackle the different projects in a systematic and integrated manner (Joslin & Müller, 2015).
Due to the use of methodology, it would be able to provide many of the benefits at the
tactical, strategic and operational levels.
2. (a) Different Project Methodologies and Processes
Project Management Body of Knowledge (PMBOK) – It is defined as the set of
standard guidelines and terminology for the use in project management. It could also be
defined as the complete collection of different processes, terminologies, guidelines that
would be accepted as the standards within the industry of project management (Burke, 2013).

2PROJECT MANAGEMENT METHODOLOGIES
PRINCE2 – It is abbreviated as Projects IN Controlled Environments. This is a
structured method of project management and program for certification of the practitioner.
This methodology focusses on the dividing of project into controllable and manageable
stages.
SDLC – The Software Development Life Cycle is defined as the processes that is
mainly used by the software industry in order to design, develop and testing of high quality of
softwares.
Waterfall – It is a form of approach of linear sequential design based on certain areas
of the design of engineering. In this model, each of the phases should be completed before the
initiation of the next phases.
Agile – It is defined as the practice of continuous iteration of the process of
development and the testing of the SDLC within the project. In this methodology, the testing
and development activities are simultaneous unlike the Waterfall model.
(b) Comparison of Two Methodologies
The Similarities between Agile and Waterfall Model
In the Waterfall Model, the process would be divided into several phases. The Agile
Model would be able to propose the segregation of the development of the lifecycle
(Moniruzzaman & Hossain, 2013).
The Differences between Agile and Waterfall Model
The Waterfall Model is structured into the methodology of software development,
which is rigid. The Agile methodology provides a flexible approach (Stoica, Mircea &
Ghilic-Micu, 2013).

3PROJECT MANAGEMENT METHODOLOGIES
3. Relation of the Chosen Methodologies to the Project Life Cycle (PLC)
The Agile methodology introduces the iterative process rather than using the
sequential process. As the requirements are changing, hence flexible approaches are very
much necessary for the Life Cycle of the Project. The Agile approach grips the constant
changes within the projects that would occur within the development of newer forms of
technology. This would allow the software development teams to divide the lengthy
requirements into several segments, build and then test the several phases of the small
segments. This would help in the delivery of the software in a quicker process.
The Waterfall Model would rather focus on the logical progression of the different
steps throughout the entire life cycle of the project (Chhim, Chinnam & Sadawi, 2017). The
developers who would be developing the project would be moving to the next step after the
successful completion of the previous steps within the methodology. Hence there would be
no chances of making errors. Hence the outcome and the detailed plan of the project should
be set properly at the initiation of the project.

4PROJECT MANAGEMENT METHODOLOGIES
References
Burke, R. (2013). Project management: planning and control techniques. New Jersey, USA.
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.
Moniruzzaman, A. B. M., & Hossain, D. S. A. (2013). Comparative Study on Agile software
development methodologies. arXiv preprint arXiv:1307.3356.
Stoica, M., Mircea, M., & Ghilic-Micu, B. (2013). Software Development: Agile vs.
Traditional. Informatica Economica, 17(4).