Project Management Methodologies
Project Management Methodologies
Home
Product
Examples
Marketing
Marketing agencies
Product development
Project managers
Team leaders
Success stories
Pricing
Enterprise
Blog
Login
Login
Project Management Guide
The Ultimate Introduction to Project Management Fundamentals
Overview
Methodologies
Team preparation
Project tools
Collaboration Tips
Manage Your Projects
Resources
Glossary
FAQ
About PMBOK
https://www.wrike.com/project-management-guide/methodologies/ 1/10
5/31/2017 II. Methodologies - Project Management Guide
If youre looking for a quick visual guide to popular methodologies, then check out the blog post and infographic: 16
Top Project Management Methodologies (Infographic).
CONTENTS
1. The Top Project Management Methodologies
+ Waterfall
What is the most common way to plan out a project? Sequence the tasks that lead to a nal deliverable and work on
them in order. This is the Waterfall methodology the traditional method for managing projects and the one that is
simplest to understand. One task must be completed before the next one begins, in a connected sequence of items that
add up to the overall deliverable. Its an ideal method for projects that result in physical objects (buildings, computers),
and project plans can be easily replicated for future use.
The power of this methodology is that every step is preplanned and laid out in the proper sequence. While this may be
the simplest method to implement initially, any changes in customers needs or priorities will disrupt the sequence of
tasks, making it very difcult to manage.
https://www.wrike.com/project-management-guide/methodologies/ 2/10
5/31/2017 II. Methodologies - Project Management Guide
+ Critical Path Method (CPM)
The critical path method developed in the 1950s is based on the concept that there are some tasks you cant start until a
previous one has been nished. When you string these dependent tasks together from start to nish, you plot out your
critical path.
Identifying and focusing on this critical path allows project managers to prioritize and allocate resources to get the
most important work done, and reschedule any lower priority tasks that may be clogging up your teams bandwidth.
This way, if changes need to be made to the project schedule, you can optimize your teams work process without
delaying the end results.
Further Reading:
Critical chain project management is a methodology that puts a primary focus on the resources needed to complete the
projects tasks. It begins by building a project schedule and identifying the most crucial tasks that need to be done
the Critical Chain and reserving resource for those high-priority tasks. It also builds buffers of time around these
tasks into the projects schedule, which helps ensure the project meets its deadlines.
Project management purists however insist that PMBOK is not so much a methodology as it is an agreed upon set of
standards and conventions for managing projects. A similar analogy is that the dictionary is not a method for creating
books, but it collects the agreed-upon vocabulary used to write books.
Read the section About PMBOK for a deeper discussion on the 5 process groups and the 10 key knowledge areas.
After Waterfall and PMI/PMBOK, another popular project management methodology is Agile and the various
frameworks with which to implement Agile. Lets take a look at some of them.
+ Agile
The core of the Agile methodology was developed by 17 people in 2001 in written form. Their Agile Manifesto of
Software Development put forth a groundbreaking mindset on delivering value and collaborating with customers.
Agiles four main values are expressed as:
Today, the word Agile can refer to these values as well as the frameworks for implementing them, including: Scrum,
Kanban, Extreme Programming, and Adaptive Project Framework.
https://www.wrike.com/project-management-guide/methodologies/ 3/10
5/31/2017 II. Methodologies - Project Management Guide
What is common among the various avors of Agile? Project objectives are made clear by the customer while the nal
deliverable can change. The project team works in iterative cycles, always evaluating results at the end. Depending on
the results of these evaluations, the nal deliverable may be modied in order to better answer the customers needs.
Continuous collaboration is key, both within the project team members and with project stakeholders.
Further Reading:
+ Scrum
Scrum is the most popular Agile development framework because it is relatively simple to implement but also because
it solves a lot of problems that software developers have struggled with in the past such as convoluted development
cycles, inexible project plans, delayed production.
In Scrum, a small team is led by a Scrum Master whose main job it is to clear away all obstacles to work getting done
more efciently. The team works in short cycles of two weeks called sprints, though the team members meet daily to
discuss whats been done and where there are any roadblocks that need clearing. This methodology allows for quick
development and testing, especially within small teams.
Further Reading:
+ Kanban
Kanban is another framework for implementing Agile but is based on a teams capacity to do work. It originated from
the factories of Toyota during the 1940s and was originally a visual system of cards (kanban) used by a department
to signal that their team is ready for more raw materials, that the team has more capacity to produce.
Today, this visual approach to managing a project is well-suited to work that requires steady output. Project teams
create visual representations of their tasks often using sticky notes and whiteboards (though there are also virtual
versions that can be used online) and move these through predetermined stages to see progress as it happens and
identify where roadblocks occur.
Extreme programming is another offshoot of Agile and is a methodology designed to improve the quality (and
simplicity) of software and the ability of a development team to adapt to customers needs. Much like the original
Agile formula, XP is characterized by short work sprints, frequent iterations, and constant collaboration with
stakeholders. Change can happen within a sprint: if work hasnt started on a certain feature, it can be swapped out and
replaced by a similar task.
Adaptive Project Framework grew from the view that most IT projects cant be managed using traditional project
management methods, due to uncertain and changing requirements.
https://www.wrike.com/project-management-guide/methodologies/ 4/10
5/31/2017 II. Methodologies - Project Management Guide
Thus APF begins with a Requirements Breakdown Structure (RBS) to dene strategic project goals based on product
requirements, functions, sub-functions, and features. The project proceeds in iterative stages, and at the end of each
stage, teams evaluate previous results in order to improve performance and practices. Stakeholders can also change the
projects scope at the start of each stage in order for the team to produce the most business value.
The underlying idea behind event chain methodology is that there are potential risks that often lie outside the projects
scope. Its important to prepare for these risks and plan what to do if they occur. Why? Unexpected events will impact
your projects schedule, deliverables, and potentially its success.
Extreme project management (XPM) is the opposite of Waterfall in that it offers you a way to manage massive change
and still move forward to project completion. In XPM, you can alter the project plan, budget, and even the nal
deliverable to t changing needs, no matter where the project is. Its the perfect way to manage projects that have a
short timeline of anywhere from a few weeks to mere days.
Further Reading:
Then there are the project management methods which practically veer into the areas of business process management
(BPM) wherein each method focuses on work as a collection of processes. While project management purists may
argue that these methods belong on some other list, we argue that these are still quite valid ways to plan for and
execute a project plan.
+ Lean
Lean is a methodology that is focused on streamlining and cutting out waste. The rst step is to create a work process
breakdown to identify and eliminate bottlenecks, delays, and all forms of waste (muda). The goal is to do more with
less: i.e. deliver value to the customer using less manpower, less money, and less time.
Further Reading:
+ Six Sigma
Six Sigma is a statistics-based methodology that seeks to improve the quality of a process by measuring the defects or
bugs present and getting it down as close to zero as possible. A process can therefore attain a rating of Six Sigma if
99.99966% of the nal product your project deliverable is defect-free.
https://www.wrike.com/project-management-guide/methodologies/ 5/10
5/31/2017 II. Methodologies - Project Management Guide
Combining the minimalist approach of Lean (no waste!) and the quality improvement of Six Sigma (zero
defects!), Lean Six Sigma focuses on eliminating waste so that projects are more efcient, cost effective, and truly
answer customers needs.
Process-based Project Management is a methodology that aligns all project objectives with a companys larger mission
and corporate values. Thus all project goals and tasks remain strategic, and must roll up to the larger corporate
objectives. The actual steps involved include: dening the process, establishing metrics, measuring processes, and
adjusting objectives when these prove unstable, planning improvements and then implementing them.
+ PRINCE2
PRINCE2 stands for Projects In Controlled Environments. Its a method for managing projects used by the UK
government and characterized by a product-based planning approach. In PRINCE2, high level activities such as setting
the business justication and resource allocation are owned by a structured project board while a project manager takes
care of the lower level, day-to-day activities such as scheduling. This methodology gives teams greater control of
resources and the ability to mitigate risk effectively.
Further Reading:
+ PRiSM
First off, this is not the surveillance program of the same name initiated by the US National Security Agency. Instead,
PRiSM stands for Projects Integrating Sustainable Methods and is a project management methodology that is aimed at
managing change while incorporating environmental sustainability into its processes. The goal with PRiSM is to
complete projects while reducing a companys negative environmental and social impact. It is, quite literally, green
project management.
+ Benets Realization
From conception to execution to delivery and beyond, the Benets Realization methodology focuses on whether your
deliverable satises the benets the customer is expecting to get from it, not just whether or not a product was
delivered on time or within budget. This methodology ensures that you deliver real value to customers and
stakeholders.
Take a look at your requirements, your project goals and objectives. What does your nal deliverable need to look
like? What benets should it provide? Some examples:
If its a physical object such as a building or a household product with very denite materials and clear
stakeholder expectations, it may benet from a sequential methodology such as Waterfall or Critical Path.
If its a software product or an app that is not set in stone yet, a exible Agile methodology may be just what the
project needs.
https://www.wrike.com/project-management-guide/methodologies/ 6/10
5/31/2017 II. Methodologies - Project Management Guide
Is environmental sustainability a core value of the organization and essential to the delivery of your product?
Then look at PRiSM.
Is rapid development of a minimum viable product the most important thing? Then look at one of the process-
based methodologies such as Lean or Lean Six Sigma.
If they thrive on collaboration, incorporating new ideas as they work, and even last-minute pivots due to
changing needs, then consider methodologies such as Scrum, Kanban, XP, or APF.
Or do they prefer an orderly, structured plan that accomplishes tasks sequentially? Then look at methodologies
such as Waterfall, Critical Path, and Critical Chain Project Management.
The Beginners Guide to Project Management Methodologies: Download our free ebook that digs into the pros
and cons of 16 top project management methodologies.
Now that youve been introduced to the various methodologies, the next step is to prepare your team members to work
together. This means building up the right team habits and mindsets so that work can be done smoothly and with a
minimum of friction.
In the next section, we tackle how to prepare your team to work as a cohesive unit.
or Save as PDF
Power Your Team's Collaboration!
Enter your business email Get started for free
https://www.wrike.com/project-management-guide/methodologies/ 7/10
5/31/2017 II. Methodologies - Project Management Guide
About
Company
Careers
Blog
Newsroom
Contact Us
Wrike
Product
Pricing
Customers
Integrations
API
Security
Solutions
Marketing
Creative
Project Management
Product Development
All Teams
https://www.wrike.com/project-management-guide/methodologies/ 8/10
5/31/2017 II. Methodologies - Project Management Guide
Resources
For Marketers
For Productivity
For Collaboration
For customers
Help Center
Webinars
Community Forums
Consultation Services
Translation Portal
For partners
Afliate Program
https://www.wrike.com/project-management-guide/methodologies/ 9/10
5/31/2017 II. Methodologies - Project Management Guide
Follow us
Language: English
https://www.wrike.com/project-management-guide/methodologies/ 10/10