Project Management Methodologies: Organizations and Solutions

This report examines project management methodologies, focusing on their application within different organizational contexts. It begins with an introduction to project management methodologies, outlining their importance and various types, including Adaptive project framework, Agile software development, Crystals methods, Dynamic system Development Model, Extreme programming, Feature Driven development, lean development, Prince2, Rapid Application Development, Spiral, System development life Cycle (SDLC), Waterfall (Traditional). The discussion section analyzes the implementation of specific methodologies – PMI/PMBOK, critical chain management, and waterfall method – within three distinct organizations: a financial services firm, a building society, and an IT services company. The report details the implementation processes, highlighting the advantages and disadvantages of each methodology in its respective setting. It then addresses the issues that arise during implementation, such as process lags, commitment challenges, and inflexibility, and proposes solutions tailored to each organization. The report concludes by summarizing the benefits of the methodologies and emphasizing the importance of selecting the right approach based on project requirements.

Running head: PROJECT MANAGEMENT METHODOLOGY
PROJECT MANAGEMENT METHODOLOGY
Name of the Student:
Name of the University:
Author note:

1PROJECT MANAGEMENT METHODOLGY
Table of Contents
Introduction..........................................................................................................................3
Discussion............................................................................................................................4
Implementation process.......................................................................................................6
Organization A.................................................................................................................6
Organization B.................................................................................................................7
Organization C.................................................................................................................8
Issue with Implementation...................................................................................................9
Organization A.................................................................................................................9
Organization B...............................................................................................................10
Organization C...............................................................................................................10
Solution to issue.................................................................................................................11
Organization A...............................................................................................................11
Organization B..............................................................................................................11
Organization C...............................................................................................................12
Benefit of Methodologies..................................................................................................12
Organization A...............................................................................................................12
Organization B...............................................................................................................12
Organization C...............................................................................................................13
Conclusion.........................................................................................................................14

2PROJECT MANAGEMENT METHODOLGY
References..........................................................................................................................15

3PROJECT MANAGEMENT METHODOLGY
Introduction
Project Management Methodology is mainly used by manager to achieve goals and desired
outputs with in a definite period of time. Irrespective of its field there are certain
methodologies which the managers follow from initiation to its implementation. A
methodology is nothing but a design which is used by project managers for designing,
planning, achievements and implementation of their project goals. There are large number of
project management methodology which can be used to benefit the various ongoing projects.
There is a particular methodology that NASA uses to build up a space station which
completely differs from the methodology used by Navy to build submarines. There is various
project management methodology that are used to satisfy the needs of different projects
across various domains of business.
The most commonly used project management methodology are Adaptive project
framework, Agile software development, Crystals methods, Dynamic system Development
Model, Extreme programming, Feature Driven development, lean development, Prince2,
Rapid Application Development, Spiral, System development life Cycle (SDLC), Waterfall
(Traditional).
Selecting the appropriate project management could be bit risky because it involves a lot of
factors that should be considered. Each project management methodology has its own
positive and negative aspects. There is no as such term called good or bad methodology, it
totally depends on the requirement of the project.

4PROJECT MANAGEMENT METHODOLGY
Discussion
Implementation of project management methodology in Organization A, which mainly deals
in providing financial services. The organization A is a small organization which its total
employee ranges of 80. Managers from different organization of same domain are more
focused to achieve certain goals and target within a specified time. In the domain of financial
services, there are variety of requirements that much be checked for ensuring the nature of
the industry. This industry can be considered to be fast and more complex. In financial
industry, the running of various projects involves money of other people. Both the process
and the result involve constant careful attention to ensure the funds containing money of
various organization are not mishandled. Due to the above-mentioned reasons, it is
important that the appointed manager should be enough qualified and honest to manage all
the necessary projects from different domain. In this type of organization project
management like PMI/PMBOK should be best as the best way to approach different project
process.
Implementation of project management methodology in Organization B, which mainly deals
in building society. The organization B is an organization which incorporates an employee
range of 600. It is the duty of project manager to provide project management services and
manage the changes in a better way using the various methods of project management. It is
the duty of the jobholder to manage all the ongoing projects to draw conclusion and set time
scales, budgets and quality of the implementation of new ideas with systems. The ultimate
goal is to manage the expectation of various business models and to ensure that all the risk of
the projects is highlighted and managed properly. It is the duty of the project manager to
work broadly with various supplier from third party. It also ensures to create and manage all

5PROJECT MANAGEMENT METHODOLGY
the relationship with various leading partners. Building society include the following steps
like regular reporting of a project to Senior project executive, project groups. Working with
the various project director to give specific information about the implementation of various
methods that can be used to check the key points of the project. It also ensures that all the
issues related to project are raised among project managers to ensure that it does not provide
risk to any person. It also ensures to resolve conflict related to resource by adjusting the
priority of various project task through meetings with various managers to improve the
regions of weakness.
Fig 1: Project management methodology

6PROJECT MANAGEMENT METHODOLGY
Source: (Hoffman 2012)
Implementation of project management methodology in organization C which has an
employee strength of 1200. This particular website mainly provides information Technology
services(ITS) team projects which mainly focuses to provide certain set of standards which
can be used to initiate and manage different projects. It mainly focuses to provide reasonable,
flexible and accessible domains. By considering the conditions waterfall method can be
considered best for project approach. The ultimate goal is to break the given task in a
technique such a way that it can task can be can be completed in a better way.
Implementation process
Organization A
PMI/PMBOK can be considered as the method for organization A as it involves the total
participation and the its working is can be considered as just one-just manner. Basic process
involved in this process is initiation, planning, execution, monitoring and controlling. In the
initiation phase the main goal is to provide aim of the total project (Hoffman 2012). The next
phase mainly involves the planning about the technique of different project and to check the
different process involved for satisfying the requirement of given projects (Hoffman 2012).
The execution phase mainly checks the requirement of different projects. In many case the
overall cost of the project is also decided (Kerzner 2013). Monitoring phase mainly checks
the total working principle of project with controlling the different measures in order to get
proper outputs or results. The next phase that is closing phase mainly checks the various
requirements of the given project (Katz and Calasanti 2014). The fact should be considered

7PROJECT MANAGEMENT METHODOLGY
that the monitoring phase should be put in every phase in order to cut the different bugs at the
end.
Fig 2: PMI/PMBOK MODEL
Source: (Kerzner 2013)
Organization B
Critical chain management methodology can be considered as the best methodology that
can be implemented for the process of planning, execution and managing other projects
which multi as well as single handed environment (Kerzner 2013). Critical chain can be
taken as a path of different task that are dependent. The term dependent mainly focuses to
involve task and projects taking into account about the various dependencies with respect to
task (Kerzner 2013). With stress on the time wasting and it also checks the various risk
associated with it. The procedure of chain management system mainly focuses to implement

8PROJECT MANAGEMENT METHODOLGY
a technique to the estimate the required time for the project (Martinell and Milosevic 2016).
The ultimate goal is to cut the time required into half the regular estimation which is
implemented in general (Martinell and Milosevic 2016). Critical chain management mainly
uses the concept of buffer in order to reduce its direct effect and also checks the uncertainly
of the different projects Implementation of project management methodology in Organization
B, which mainly deals in building society (Martinell and Milosevic 2016). The organization
B is an organization which incorporates an employee range of 600. It is the duty of project
manager to provide project management services and manage the changes in a better way
using the various methods of project management. It is the duty of the jobholder to manage
all the ongoing projects to draw conclusion and set time scales, budgets and quality of the
implementation of new ideas with systems.
Fig 3: Critical Method
Source: (Matos and Lopes 2013)
Organization C
Waterfall method can be considered as very good method. There are some minor changes
that must be there in description and it must check the number of steps involved in the

9PROJECT MANAGEMENT METHODOLGY
waterfall model. The overall idea is to focus on the same point. During the requirement phase
all the important requirement must be taken into consideration which directly relates to the
working principle of the projects (Matos and Lopes 2013). In waterfall model, the basic
requirements are written in a file which is known as requirement documents (Matos and
Lopes 2013). The next phase that is analysis phase of the system mainly focuses to generate
the various models of business that are designed for working of various application (Mishra,
A. and Dubey, D., 2013). The design model mainly adds the design phase (Mishra, A. and
Dubey, D., 2013). After the successful implementation of the design phase, the coding phase
is implemented and after the successful output of the coding phase (Mishra, A. and Dubey,
D., 2013). After that total software is tested for bugs or any faults from developer’s side
(Matos and Lopes 2013).
Fig 4: Waterfall Method
Source: (Snyder 2014)

10PROJECT MANAGEMENT METHODOLGY
Issue with Implementation
Organization A
With growing use of PMI/PMBOK model in different sectors the process consisting a
series of task lags behind and this can be considered as one of the method involving the
model by management. The pre-judging of idea cannot be handled by various models which
aims to provide implementation related issue that can be avoided so the developed project
does not create any issue in the near future. In financial industry, the running of various
projects involves money of other people. Both the process and the result involve constant
careful attention to ensure the funds containing money of various organization are not
mishandled. Due to the above-mentioned reasons, it is important that the appointed manager
should be enough qualified and honest to manage all the necessary projects from different
domain. In this type of organization project management like PMI/PMBOK should be best as
the best way to approach different project process.
.
Organization B
Critical chain project management is considered to be a comprehensive process. It mainly
requires a lot of involvement from perspective of the whole organization. In the present
scenario, the commitment is very much extensive (Obrutsky 2014). The commitment should
be considered from the perspective of the team of the projects that from project managers to
project stakeholders (Obrutsky 2014). The following point must be considered into account
that entire process should be clear and the basic point of view that must be underline which
should be understood very clearly (Obrutsky 2014). Without proper critical chain
management, a project may fail as an it will directly use the method. Now a broken

11PROJECT MANAGEMENT METHODOLGY
implementation of critical chain method will provide no or little benefits over the prevision
techniques of implementation as it will ensure an overhead cost.
Organization C
Waterfall method does not require much revision or reflection. One thing that must be
considered for waterfall method that it is very much difficult or almost impossible to bring
out any changes (Snijders Wuttke and Zandhuis 2012). This is mainly done to check
everything is in good condition or not. In many cases it is observed that during late life cycle
phase only working software is produced and which is not done before the implementation of
other phases into it (Snijders Wuttke and Zandhuis 2012). When it comes to object oriented
projects or complex projects waterfall method cannot be considered as the most appropriate
one (Snijders Wuttke and Zandhuis 2012). For long and ongoing projects, it is considered to
be an inappropriate one. This model is not good suitable for projects where the overall
necessity of the project is in moderate and liable (Suárez-Figueroa Gómez-Pérez and
Fernández-López 2012).
Solution to issue
Organization A
PMI/PMBOK model helps in keeping a track of the different ongoing activities in an
organization (Suárez-Figueroa Gómez-Pérez and Fernández-López 2012). It mainly focuses
to establish a standard of working among various organization. The provides an important
key factor which will ultimately help in managing (Suárez-Figueroa Gómez-Pérez and
Fernández-López 2012). The risk management method is checked carefully with the
implementation of PMI/PMBOK due to the factor of documents (Suárez-Figueroa Gómez-

12PROJECT MANAGEMENT METHODOLGY
Pérez and Fernández-López 2012). The concept also checks the various implementation that
is not suitable for working. It is also stated that with successful working of PMI/PMBOK the
project manager can adjust the activity towards any project (Stoica ,Mircea and Ghilic-Micu
2013).
Organization B
Critical chain project management which can be useful to improve the various condition
of project management plan (Stoica, Marcia and Ghilic-Micu 2013). With this project
management methodology the project delivering reliability can be improved to a lot of
extent. It also helps in handling delivering data ideas that can be checked by reducing the
overall project duration time (Stoica, Mircea and Ghilic-Micu 2013). Threats play an
important role in various project management concept as it checks any bugs or errors that can
be identified in the deployment phase of the software (Stoica, Marcia and Ghilic-Micu 2013).
This particular methodology gives an early warning before the actual arising of problem.
This particular problem can directly affect the project delivery time and other factors which
are needed for correction of bugs and rectification of various faults in the given
software.
.
Organization C
Waterfall method allows managerial control over the given software. The overall idea of
this model is considered to be very easy for understanding and using. This model is mainly
used in the regions where the requirement of the projects is well understood, the aspects and
idea is clearly pointed out.

13PROJECT MANAGEMENT METHODOLGY
Benefit of Methodologies
Organization A
The benefits that can be gained from the use of PMI/PMBOK model are:
 Easy breakdown of project management steps.
 PMBOK checks the updating and developments of various professional
bodies.
 It mainly focuses on the expansion of various industry
 PMBOK methodology is recognized on a global basis.
 Project management team reduces the overhead cost.
Organization B
The benefits that can be achieved by the use Critical chain project
management are:
 Parkinson’s Law: It mainly ensures expansion of time in order to
reduce pressure of work.
 Syndrome Student: When the deadline of a project is near then the
respective workers start giving their cent percent.
 Murphy’s Law: This law ensures that when an aspect go in a wrong
direction then it will ultimately go in that particular direction.
 Multi-tasking Bad: The beginner of a given project or task can affect
concept of bad multitasking.
Organization C
Waterfall model can bring certain benefits like:

14PROJECT MANAGEMENT METHODOLGY
 This model is considered to be very much easy for working and it
also limits the amount of resources.
 In this model after each and every process the concept may appear
to be very much visible. The concept also checks that projects are
in progression.
 This method is considered to be better as it contains a large number
of stages like analysis, design, coding and maintenance.
 This methodology is considered in cases where quality is ahead of
schedule and cost.
Conclusion
From above discussion, it can be concluded that there is various business model that must
be implement in the total working of the software projects. Each and every model comprises
of some advantages and disadvantages. Each methodology has its own positive sides like
waterfall method can be used for developing software while PMBOK can be used in the
financial sectors. The concept also checks the various implementation that is not suitable for
working. It is also stated that with successful working of PMI/PMBOK the project manager
can adjust the activity towards any project (Stoica, Marcia and Ghilic-Micu 2013). Each
project management methodology has its own positive and negative aspects. There is no as
such term called good or bad methodology, it totally depends on the requirement of the
project (Kogan , Martinelli and Milosevic 2016).

15PROJECT MANAGEMENT METHODOLGY
References
Hoffman, A.S., 2012. Hydrogels for biomedical applications. Advanced drug delivery
reviews, 64, pp.18-23.
Katz, S. and Calasanti, T., 2014. Critical perspectives on successful aging: Does it “appeal
more than it illuminates”?. The Gerontologist, 55(1), pp.26-33.
Kerzner, H., 2013. Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Kogan Page Publishers. Martinelli, R.J. and Milosevic, D.Z., 2016. Project management
toolbox: tools and techniques for the practicing project manager. John Wiley & Sons.
Matos, S. and Lopes, E., 2013. Prince2 or PMBOK–a question of choice. Procedia
Technology, 9, pp.787-794.
Mishra, A. and Dubey, D., 2013. A comparative study of different software development life
cycle models in different scenarios. International Journal of Advance research in computer
science and management studies.
Obrutsky, S.L., Comparison and contrast of project management methodologies PMBOK and
SCRUM.
Snijders, P., Wuttke, T. and Zandhuis, A., 2012. Pocket Companion to PMI's PMBOK
Guide-Updated Version. Van Haren Publishing.
Stoica, M., Mircea, M. and Ghilic-Micu, B., 2013. Software development: Agile vs.
traditional. Informatica Economica, 17(4), p.64.

16PROJECT MANAGEMENT METHODOLGY
Suárez-Figueroa, M.C., Gómez-Pérez, A. and Fernández-López, M., 2012. The NeOn
methodology for ontology engineering. In Ontology engineering in a networked world (pp. 9-
34). Springer Berlin Heidelberg.