Agile Methodology and PMBOK Comparison

This assignment compares Agile methodology and PMBOK (Project Management Body of Knowledge) in the context of project management. It discusses the differences between the two approaches, including their respective stages, advantages, and applications. The comparison highlights that Agile is a more beneficial approach for modern project development due to its adaptability and ease of use. The assignment also references relevant studies and papers to support its claims.

Running head: AGILE METHODOLOGY AND PMBOK
AGILE METHODOLOGY AND PMBOK
Name of the Student:
Name of the University:
Author Note:

1
AGILE METHODOLOGY AND PMBOK
Project Management Methodology
Project management methodology provides different tools for the project managers in
order to complete the project efficiently. The methodologies are the well-defined
logicalprocesses, which contains orderly steps (Snyder, 2014). Those steps are needed to be
followed in the compilation phase of the project in order to get the desired result. There are
different methodologies for the project compilation .Choosing of the methodology depends on
the type of project. All the methodologies generally follow the guidelines mentioned in the
PMBOK. The project methodologies help the project managers to follow the tasks sequentially
so that the execution of the project can be done in time maintaining the estimated cost.
Role of Project Management Methodology:
It helps the project managers to develop and execute the project within the defined time.
Maintaining the methodology also helps the project to meet every details mentioned in the
requirement. The general guidelines help achieve desired attributes of the project.
PMBOK:
Project Management Body of Knowledge is the general guideline which defines the
desired attributes of a project methodology and it also mentions the basic stages of compilation
of the project. The guidelines of PMBOK is globally accepted. The first two chapters of the
PMBOK guideline consists of the general definitions of different components of project
management. The necessary tools and methods for the management of the project has been
described from chapter 4 to chapter 12. The application of PMBOK for evaluation of the
management methodology includes five steps. These steps are- initialization of the project or the
starting of the project, planning of the project compilation, execution of the plan, controlling and

2
AGILE METHODOLOGY AND PMBOK
monitoring the status of the project and the last step is closing of the project. All these steps are
inter-related to each other.
Agile Project Management Methodology:
Agile project management methodology is considered the modern methodology for the
project management. It is the form that can be derived from merging SDLC with the iteration. In
case of project methodology there are many conventional models like waterfall model which
were followed before (Sverrisdottir, Ingason&Jonasson, 2014). The advancement of technology
has increased and changed the requirement of the project. In this case applying agile
methodology is helpful. In Agile methodology the end users and the developers work together in
order to determine the priority of the required feature of the project (Tsai et al., 2016). The main
focus of this methodology is the progress of the project and this methodology encourages face to
face communication in order to get a clearer view of the requirement of the project. The agile
methodology defines the combination of various methodology under one name.
Agile system development has four categories-
 Product
 Customer
 Performance
 Team of the project
Mainly there are two agile methods, they are-scrum and extreme programming (XP).
In case of extreme programming the user requirements re documented as the user stories
(Abrahamsson et al.,2017). User stories are then transferred into object oriented modelling

3
AGILE METHODOLOGY AND PMBOK
environment called class diagram. The whole system is then transferred into a series of versions
called releases.
In scrum methods there are three important roles available-
 Scrum master- This role is similar to the role of project manager
 Product Owner- The role of this part is to ensure that the project has met all the
requirements.
 Development team- The development team is responsible for delivering the quality
project in time.
There are few terms, which are related to the scrum method of agile methodology.
Product Blockage: The team decides the priority of the features in the project.
Sprint- It defines the iteration that is presents for a timespan and after that the delivery of the
complete project is done.
Daily Scrum- It defines the short meetings between the stakeholders of the project in order to
understand the requirement more clearly.
Advantages of Agile method:
Agile methodology ensures high product quality as there are several methodology is used
in the agile method. Using agile method in project development, higher customer satisfaction can
be received as the requirement of the project is discussed between the users and the developers.
It reduces the risk involved in the project and increases control over the project.
Comparison between Agile methodology and PMBOK
Stages Agile PMBOK

4
AGILE METHODOLOGY AND PMBOK
Starting of project This step is known as the vision
statement. In this stage
determination of timeline of the
iteration, goals and the
formation of team are decided.
In PMBOK this stage is known
as initialization
stage(Ghosh,2015). In this stage
the goal and objective of the
project is determined.
Planning Release plan for the particular
version is done in the beginning
of the project and the sprint
planning is done throughout the
project.
Plans to execute the project are
created at the initial stage of the
project and updating of the plans
happens throughout the project
running phase.
Execution of the project This stage is known as team
driven development in agile
methodology (Ahimbisibwe,
Cavana& Daellenbach,2015).
Team development works on the
product blockage and the
product owner determines the
user story on which the sprint
needs to be done. In this case the
tools used are- story
prioritization and sprint
blockage.
In the execution phase of
PMBOK the plans, which were
determined at the beginning of
the project are executes in the
execution phase.
Controlling and monitoring of
the project
In agile methodology time and
cost of the project are fixed.
Only the changes in the project
There are four constrains-
cost,time,risk and quality are
monitored and controlled

5
AGILE METHODOLOGY AND PMBOK
is monitored and controlled. throughout the time span.
Closing of the project There is no formal closing and
feedback taking process in agile
model. Instead of that
retrospective meeting is
organized in order to determine
the further modification on the
project.
Formal closing of the project is
done in the PMBOK (Landry &
McDaniel, 2016). The feedbacks
about the project are taken after
the evaluation of the project.
Identification of Agile method with PLC:
Figure 1: Agile methodology and PLC
(Source: Landry & McDaniel,2015)
The Determination of preferable approach:
The discussion and the comparative study between agile and PMBOK indicate that the
application of agile methodology in order to develop a project is more beneficial
(Landry&McDaniel,2015). PMBOK contains the traditional framework of project management,

6
AGILE METHODOLOGY AND PMBOK
whereas the advancement of technology has changed the requirement of the project and there are
changes happening in the way of developing a project. Agile methodology is the improved and
modernized version of the project management which enables the new methodology of
completing the project, which is realistic and easy to follow.
References

7
AGILE METHODOLOGY AND PMBOK
Abrahamsson, P., Salo, O., Ronkainen, J., &Warsta, J. (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Ahimbisibwe, A., Cavana, R. Y., &Daellenbach, U. (2015). A contingency fit model of critical
success factors for software development projects: A comparison of agile and traditional
plan-based methodologies. Journal of Enterprise Information Management, 28(1), 7-33.
Ghosh, S. (2015). Systemic Comparison of the Application of EVM in Traditional and Agile
Software Project. Integration, 5, 3.
Landry, J. P., & McDaniel, R. (2015). Agile Preparation Within a Traditional Project
Management Course. In Proceedings of the EDSIG Conference (p. n3429).
Landry, J., & McDaniel, R. (2016). Agile Preparation Within a Traditional Project Management
Course. Information Systems Education Journal, 14(6), 27.
Snyder, C. S. (2014). A guide to the project management body of knowledge: PMBOK (®)
guide. Project Management Institute: Newtown Square, PA, USA.
Sverrisdottir, H. S., Ingason, H. T., &Jonasson, H. I. (2014). The role of the product owner in
scrum-comparison between theory and practices. Procedia-Social and Behavioral
Sciences, 119, 257-267.
Tsai, J., Ho, C. Y., Chang, J., & Jiang, J. (2016). The Role of Agile Methodology Use and
Feedback Attributes in Game Development Projects: Implications for Game Project
Quality.