Project Management Body of Knowledge (PMBOK) Guide

EXECUTIVE SUMMARY
The objective of this report is to evaluate and compare a generic set of project management
methods as defined in PMBOK (Project Management Body of Knowledge) with agile project
management methods.PMBOK is a guide developed by PMI (Project Management Institute)
and it is structured around five processes (initiating, planning, execution, controlling and
closure) and ten knowledge areas (scope management, time management, cost management,
quality management, human resource management, risk management, communication
management, integration management, procurement management, stakeholder management).
On the other hand, Agile is a time boxed, iterative approach to project delivery that builds it
incrementally from the start of the project, instead of trying to deliver it all at once near the
end. It breaks the projects into little bits of user functionality called user stories, prioritise and
then continuously deliver them in short two week cycles called iterations. Agile methodology
is based on four core principles as outlined in the Agile Manifesto. These methodologies are
rooted in adaptive planning, early delivery and continuous improvement, all with an eye
toward being able to respond to change quickly and easily. The report will explain PMBOK
project management processes and agile project management processes, their comparison,
applicability and the conclusion. Each project is having different requirements hence project
manager may change their opinions about which is the best method from one project to the
next.
INTRODUCTION
The increasing pressure to deliver quality products in a dynamic and rapidly changing global
market forced professionals to use different methodologies for project management. There
are range of different methodologies which are applied to Project Management. This report
compares the project management method described in PMBOK guide (Project Management
Body of Knowledge) with Agile Project Management method.
1

The first part of this report will provide analysis of PMBOK processes (five process group
and ten knowledge areas) and agile project management processes with SCRUM framework,
second part will compare and contrast both methodologies, third part will explain the
applicability of both methods in different types of projects, finally the report will end with the
conclusion.
Figure 1: Project management method
(Source: 9 Project Management Methodologies Made Simple, 2017)
ANALYSIS
PMBOK method
PMBOK is considered as body of knowledge that always concentrates on applying
such process that can help in getting best results (Kerzner and Kerzner, 2017). PMBOK
includes five major phases in order to accomplish the project successfully. These stages are:
initiating, planning, execution, monitoring and closing. This technique mainly focuses on
process that is applied by project manager (PM) to complete the proposal within specified
period of time and quality. The major benefit of applying PMBOK approach is that it allows
2

business to implement standardise practices and maintain standards. This helps in minimising
risk and managing sudden constrains significantly.
Figure: PMBOK process group
(Source: The 5 PMBOK Process Groups, 2012)
 In the initiation phase, manager has to define aim and objective of particular project.
Individual has to start new task by obtaining authorization for this task (Rodriguez
and et.al., 2017).
 In planning phase, PM has to establish scope and has to refine the actual objectives.
Individual has to schedule all activities so that project can be completed on time and
with quality.
 Executing: It is the next stage in which all the planning that has been done of PM is
being executed in order to satisfy specification of project.
 Monitoring and controlling: It is the phase in which manager has to monitor
activities and have to control over it. They have to identify necessary areas that
require changes or improvement so that issues can be minimised, and project can be
accomplished with quality (Landry and McDaniel, 2015).
3
decisiongateprojectcharterINITIATINGdecisiongateprojectplanPLANNINGdecisiongateprojectauidtCLOSING

 Closing is the last stage in which all the tasks are being finalised and it is formal way
to close the project.
project management is concerned with fulfilling the demands of scope, time, cost, quality and
risk followed by predetermined stakeholder requirements through the application of ten
knowledge areas: Scope Management, time management, quality management, cost
management, human resource management, risk management, procurement management,
integration management and communication management. These knowledge areas include
various processes and functions performed by the project managers and team throughout the
various stages of the project to ensure successful delivery of project.
Figure 2: PMBoK knowledge areas
(Source: The 10 PMBOK Knowledge Areas, 2016)
4
Knowledge areas of
PMBOK