Project Management Methodologies: A Comparative Analysis of Two Models

This report delves into the realm of project management methodologies, focusing on two prominent approaches: Agile Scrum and the Waterfall model. The report begins by establishing the core principles of project management methodologies, emphasizing their role in defining the project life cycle, as guided by the Project Management Body of Knowledge (PMBoK). It outlines the five key stages of the project life cycle: initiation, planning, execution, control and design, and closing. The report then provides a detailed comparison between Agile Scrum and Waterfall, highlighting their contrasting characteristics in terms of requirement handling, project development, change management, and risk mitigation. The analysis extends to the similarities between the two methodologies, underscoring their shared commitment to enhancing product quality and adherence to PMBoK guidelines. Furthermore, the report relates the steps of each methodology to the project management life cycle, illustrating how both models incorporate all stages, albeit with different approaches. The report concludes with references to support the analysis.

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

1PROJECT MANAGEMENT METHODOLOGIES
Project management methodology helps to define the life cycle during the development
of project. The life cycle in the project management methodology is based on the guideline
mentioned in PMBoK (Project management Body of Knowledge).
Various methodologies:
Main objective of project management methodology is to develop the project in a proper
that can meet all the requirements of clients. There are various methodologies present in the
project management field (Reynolds 2018). The application of the project management
methodology is dependent on type of the project. The definite project management life cycle is
needed to be mentioned in the project management methodology (Rola, Kuchta and Kopczyk
2016). According to PMBoK project management life cycle has five different stages those
ensure the quality of the project (Rola, Kuchta and Kopczyk 2016). These five stages are-
Initialization of the project, planning, execution, control and design and closing of the project
(Karaman and Kurt 2015). The initialization phase is concerned about the gathering of the
requirement. The planning phase is defined by developing the blueprint for the execution (Rola,
Kuchta and Kopczyk 2016). The planning is based on the documentation of the requirement. It
is the responsibility of the project manager to execute the planned design or code accordingly.
The implementation of the functionality is done at the execution phase (Brioso 2015). After the
execution of the project, the evaluation of the result of the project is done through the control and
monitoring phase. The feedback is taken from the clients and users for the further improvement.
In case, if the project outcome satisfies all the requirements of the clients the closing of the
project can be done.
Selection of two project management methodologies:

2PROJECT MANAGEMENT METHODOLOGIES
In order to understand the significance and the functioning of the project management
methodology, to project management methodologies have been selected. These two models are –
agile scrum and waterfall model.
Difference between waterfall model and agile scrum:
Waterfall model Agile Scrum
The requirement set is predefined and static. The set of requirement is dynamic and small.
The overall development of the project is the main
objective in this methodology.
The delivery of the of the outcome of the project is
done on the iterative basis.
The change of control is handled by the senior
project manager.
The change of control is monitored by project
management team.
Definition and scope of project are defined at the
initial stage of the project.
Regarding the resource allocation and the
development of the products daily meetings
between the team members are needed to be done
in this method.
The nature of the waterfall model is static, as no
feedback path is present.
The nature of waterfall model is flexible as the
changes can be made in each iteration.
The control and evaluation of the quality of the
final product is dine in the control and monitoring
phase.
The quality of the final product is dependent on the
quality and nature of all iterations during the
development phase.
For managing the risk , risk register and risk
management strategy are used.
For the mitigation of the risk evaluation of the
quality of all the iterations are needed to be done.
Similarities between waterfall model and agile scrum:

3PROJECT MANAGEMENT METHODOLOGIES
Both the waterfall model,agile scrum are concerned about the enhancing the quality of
the final product. Both methodologies follow the guidelines mentioned in the project
management body of knowledge(Kuhrmann et al. 2017). Both in agile scrum and waterfall
method the estimation of cost is done at initial stage of the project.
Relating the steps of methodologies and project management life cycle:
Waterfall model has different approach from agile scrum. However, in both cases all the
stages of project life cycle is present (Rola, Kuchta and Kopczyk 2016). Gathering of the
requirement is done for both cases. However, the approach for the documentation of the
requirement is different for both methodologies (Vedsmand, Kielgast and Cooper 2016). The
execution part is done iteratively in the agile scrum while the waterfall model has predefined
execution stage (Rola, Kuchta and Kopczyk 2016). The monitoring and evaluation is done for
each iteration in agile project management . On the other hand waterfall model has definite phase
for the monitoring and control of the project.

4PROJECT MANAGEMENT METHODOLOGIES
References
Brioso, X., 2015. Integrating ISO 21500 guidance on project management, lean construction and
PMBOK. Procedia Engineering, 123, pp.76-84.
Karaman, E. and Kurt, M., 2015. Comparison of project management methodologies: prince 2
versus PMBOK for it projects. Int. Journal of Applied Sciences and Engineering Research, 4(5),
pp.657-664.
Kuhrmann, M., Diebold, P., Münch, J., Tell, P., Garousi, V., Felderer, M., Trektere, K.,
McCaffery, F., Linssen, O., Hanser, E. and Prause, C.R., 2017, July. Hybrid software and system
development in practice: waterfall, scrum, and beyond. In Proceedings of the 2017 International
Conference on Software and System Process (pp. 30-39). ACM.
Reynolds, D., 2018. Can the Pmbok Solve Security Sector Reform? Using Project Management
to Achieve International Stability.
Rola, P., Kuchta, D. and Kopczyk, D., 2016. Conceptual model of working space for agile
(scrum) project team. Journal of Systems and Software, 118, pp.49-63.
Vedsmand, T., Kielgast, S. and Cooper, R.G., 2016. How new Agile-Scrum methods lead to
faster and better innovation.