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 project management methodology
Project methodology is defined by the process that defines the steps for the proper
compilation of the project (Alexandros et al., 2017). There are different methodologies those
are responsible for the proper compilation of the project. Different project methodology
follows the different approaches. However, all of these methodologies follows the steps
mentioned in the PMBOK. There are five steps mentioned in the PMBOK those are
necessary to be present in a proper methodolgy.
Role of project management methodology
The role of the project management methodology is to compile the project in such a
way that it would follow all the requirements of the clients (Alexandros et al., 2017). The
selection of the project management methodology is dependent on the type of the project. It
has been seen that the success of the project is dependent on the selection of right
methodology. The selection of the methodologies is dependent on the requirements of the
project. It is the responsibility of the project management experts to select the right
methodology for the compilation of the project (Alshamrani & Bahattab, 2015). As for
example, it can be said, for the construction project selection of the PRINCE2 methodology is
appropriate. While for the development of the complex software Agile methodology is
suitable.
Two methodologies chosen from the list
Two methodologies chosen from the list are-
Waterfall and Agile XP are the two chosen methodologies for the discussion.
Comparison between the Waterfall and Agile XP methodology
Difference between Waterfall and Agile XP methodology:

2PROJECT MANAGEMENT METHODOLOGY
Agile XP Waterfall model
This methodology is flexible This methodology is rigid in nature.
The ownership of the code is shared by the
developers.
Each modules of the work is assigned to
each of the developers.
Different iterations are delivered before the
release of the final product.
After completing one module, the starting of
another module can be done.
The whole process is light and with less
documentation.
The whole process is heavy and the proper
documentation is required.
In this methodology, the cross trained
developers are needed to take the part
(Model, 2015). They have to be
knowledgeable about all the technologies
required for the compilation of work.
Particular module is assigned to the
particular developer (Alshamrani &
Bahattab, 2015). The developer has to be
knowledgeable for the implementation of
the functionality of that particular module.
Team meetings are done in a frequent way
among the developers for measuring the
progress of the project (Alshamrani &
Bahattab, 2015).
The meeting between the developers is done
only after the handover of the module from
one developer to another.
The process is suitable for the managing the
complex software development.
The process is suitable for managing the
small projects.
Feedback path exists in the process. There is no feedback path.
For understanding the different stages in
this method expert advice is needed.
The methodology is simple and can be
understood by the novice.
Similarities between Waterfall and Agile XP methodologies