Project Management Methodology

Running head: PROJECT MANAGEMENT METHODOLOGY
Project management methodology
Name of the Student:
Name of the University:
Author Note:

1PROJECT MANAGEMENT METHODOLOGY
Definition of the methodology:
Methodology is the process that helps in the proper development of the project. The
use of the proper methodology will be help the project to deliver the desired outcome (ur
Rehman et al., 2018). There are certain steps those are needed to be followed during the
implementation of the methodology. The selection of the project methodology is based on the
type and the requirements of the project.
Role servers in project management:
The use of the proper methodology will help the project to go through certain
processes. These process will help the requirements to be accessed in a right way so that the
project can get the right outcome.
Selected methodology:
Selected two methods are agile scrum and waterfall method.
Agile scrum methodology:
Agile scrum methodology is considered as one of the agile methodologies for the
development of the project. It is an incremental and iterative method for the development of
the system or product.
Multiple sprint of time frame from 2 weeks to 1 month is present in the agile scrum
methodology. The timeline of the sprint will be maintained by scrum team during the
planning meeting (Harvie & Agah, 2016). The functionality of the proposed system is
divided into different modules. Three important aspects of scrum method are role, meetings
and artifacts. The use of agile methodology is carried out when the client is not sure about the
requirements and expects quick releases. Apart from that all the requirements are not
provided at one time.

2PROJECT MANAGEMENT METHODOLOGY
Waterfall method:
Waterfall method can be considered as the oldest project management methodology.
The waterfall method is the simplest form of method for managing the project. The first stage
of this methodology is the initialization of the project (Adiga, 2019). In this step the
requirements gathering is done. After that the analysis of the requirements are done before
the planning and execution. The testing and the deployment is done after the execution of the
project (López-Martínez et al., 2016). The developer can go to next step only after complete
compilation of the previous step. There is no way for returning back to the previous step
which makes this methodology rigid in nature. However, this method is suitable for
managing the small projects.
Comparison between two methodologies:
Difference between agile scrum and waterfall method:
Agile Scrum Waterfall
Freezes schedule Freezes scope
The collaboration with the client is
maintained throughout the process.
The collaboration of the client is done at the
beginning of the project and at the ending of
the project.
Developed the project on the basis of the
requirements of the client.
While development, considering everything
is scopes are considered.
Addition of the few features per iteration is
done in this methodology.
Designing of all the features are done.
The approach of the project is iterative. The approach of the project is linear.