PROJECT

MANAGEMENT
METHODOLOGY
Opemipo Akinmola
TYPES OF PROJECT MANAGEMENT
METHODOLOGIES
 Waterfall: It is a project management methodology that refers to the
sequential and linear ordering of phases

 Agile: refers to being able to move quickly and easily. It has to do with
flexibility and willingness to change and adopt. Projects that adopt
the Agile Project management methodology take an iterative
approach, which means the project processes are repeated many
times during the life cycle of the project. It consists of processes that
occur at a stretch within the period of the project that can be
repetitive based on the results.
 Simply put, Agile means flexibility, repetition and openness to
change.
WATERFALL MODEL
 Waterfall model is the earliest or traditional model used in software
development where the output of one phase acts as the input of the next
phase consisting of a series of steps where each steps has specific
deliverables that act as the input for the next phase, these phases are
dependent on each other
 The final version is available only after completing the entire software
lifecycle process with any deviations if available. Changes contains high risk
as changes require new revised version of the entire software running the
series of steps over again.
AGILE PROJECT
MANAGEMENT
 Agile is an approach to project and team management that embodies
agility and is based on the agile manifesto
 Agile manifesto is a collection of four values and twelve principles that
define the mindset that every agile team should strive for.
COMPARING AGILE AND WATERFALL
METHODOLOGIES

WATERFALL AGILE

 Waterfall is a strict linear  Agile embraces the reality that the world, the
process users are uncertain and unpredictable
 Agile aims to get customer feedback more
 Waterfall gets feedback at the
quickly
end
 Requirements are dynamic and open to
 It requires fixed project changes and the team receives feedback and
requirement document new information
  More person-to-person relations on agile . It has
Waterfall uses a lot of
shorter documents instead of big formal
documentation
documents
 Tangible outcome from a  Agile has smaller, more frequent release and
project are at the end of the deliverables
project
COMPARING AGILE AND WATERFALL
METHODOLOGIES
HISTORY OF AGILE
1990-2020+
HISTORY OF AGILE
 The methodology emerged organically during the 1990s by companies
desiring to build products in less time.
 Companies had to not only invent products but build the process of
inventing.
 In 2001, thought leaders and creators came together with their new
processes also methodologies to find a common ground between their
methods and solving their collective problem which was “pleasing their
customers”.
 The Leaders came up with the Agile manifestoes to guide others on
what they believe truly maters which is keeping the process flexible and
focusing on people. Both the team and the users.
 Agile wasn’t just used in the software industries but in other industries
e.g Biotechnology, media e.t.c.
AGILE MANIFESTOES
Four values, Twelve principles.
AGILE MANIFESTOES
 It consists of four values of agile

1. Individuals and interactions over processes and tools

2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan

 The twelve principle of Agile are broken into four themes

1. Value delivery
2. Business collaboration
3. Team Culture
4. Continuous learning
WHEN AND WHY DEVELOP AGILE
MINDSET
Agile works best in industries or projects that are susceptible to or that encourage
change and uncertainty e.g, Biotechnology, media, food industries, fashion etc.
 VUCA, an acronym that defines the conditions that affect organizations in a changing
and complex world, it helps industries and project know what project methodology is
best.
 V – volatility, the rate of change in a business activity.
 U – Uncertainty, refers to lack of predictability or high potential for surprise
 C – Complexity, refers to high number of interactive forces, issues, factors
affecting the project
 A – Ambiguity, Possibility of misunderstanding.
INTRODUCTION TO SCRUM
WHAT IS SCRUM?
 Scrum is developing a team to work together to develop and test a
deliverable,
 The work is completed in short cycles and the team meets daily to
discuss current tasks and clear up anything blocking the progress.

 TERMS IN SCRUM
1. Product Backlog: It is where all possible tasks , ideas, deliverables
and features are captured for the team to work with.
2. Sprint: A time boxed iteration in scrum where work is done usually
around two weeks.
3. Daily scrum: A meeting of 5 or fewer minutes everyday of sprint
WHAT IS SCRUM?
 ROLES IN SCRUM
1. Scrum master: Ensures team follows processes, shares information and helps
team focus on doing their best work.
2. Product owner: Maximize the value of product and work of the team.
3. Development team: Responsible for how to deliver that product.

 A scrum team is made up of 3-9 members

 The team members are open minded, adaptable and value continuous learning.
 Other Agile tools include
1. Kanban which means signboard
2. Extreme Programming or XP
3. Lean
THANK YOU VERY MUCH!
Opemipo Akinmola