Project management methodologies: waterfall, agile and hybrid, and how to choose

A project management methodology is a set way of running a project: how you plan it, how the work moves and how you decide what to do next. The four you will meet most are waterfall, agile, lean and hybrid. None of them is best everywhere. The right one depends on how well you know the requirements up front and how often the customer can see the work.

This guide explains each one, when it fits and how to choose. Choosing well is also a skill the PMP exam tests, so the last section covers what the exam expects.

What is a project management methodology?

A methodology is a defined way of doing the work, with its own steps, roles and documents. A framework is looser: it gives you a structure and leaves the details to the team. Scrum, for example, calls itself a framework. In practice, people use the two words interchangeably.

PMI talks about development approaches instead and groups them into three: predictive (plan-driven, like waterfall), adaptive (agile) and hybrid. PMI's PMBOK Guide is not a methodology itself. It describes good practice that you tailor to whichever approach your project uses.

Waterfall: plan first, then deliver in phases

Waterfall runs a project as a fixed sequence of phases: requirements, design, build, test and handover. Each phase finishes before the next one starts, and the scope, schedule and budget are set in a baseline near the beginning. Changes go through formal change control.

It fits when the requirements are clear and unlikely to change, and when the result cannot be delivered in pieces: a building, a bridge, a plant shutdown, or a regulated system that has to be approved as a whole. Its weakness is late feedback. The customer sees the result at the end, so a misunderstood requirement can surface just when it is most expensive to fix.

Agile: deliver in short cycles

Agile delivers the work in small, usable pieces and adjusts the plan as the team learns. Instead of a full specification up front, the team keeps a prioritised backlog, builds the most valuable items first and shows the result to the customer every cycle. Its values were written down in the Agile Manifesto in 2001.

Agile is a family of methods rather than one. The two you will hear about most:

• Scrum: work happens in sprints of one month or less, each ending with a usable increment, a review with stakeholders and a retrospective. Scrum names three accountabilities: the product owner, the Scrum Master and the developers.

• Kanban: work moves across a board from "to do" to "done", with a limit on how many items can be in progress (WIP) at each stage, so the team finishes work before starting more.

Agile fits when the requirements will change or are not fully known, and when the customer can review the work often. Software is the classic case, but product design, marketing and internal change projects use it too. It struggles when the customer is never available, or when the work genuinely cannot be split.

Lean: cut the waste

Lean project management comes from the Toyota Production System. It focuses on delivering value with less waste: less waiting, fewer handoffs and less work started but not finished. Kanban grew out of the same thinking, which is why lean and agile teams often look alike.

Lean is less a full methodology than a set of principles you can apply to any project. Map how the work flows, remove the steps that add nothing for the customer, and let demand pull work through instead of pushing it.

Hybrid: mix them on purpose

Most real projects end up hybrid. A common pattern is a predictive outer shell, with a fixed budget, stage gates and a contract, and agile delivery inside it for the parts that benefit from fast feedback. A construction project might run the build in phases while the client's booking app is built in sprints.

Hybrid works when it is designed. It fails when it happens by accident, for example when a team calls itself agile but still needs every change approved by a board that meets once a month.

Where does PRINCE2 fit?

PRINCE2 is a structured project management method, owned by PeopleCert and built on seven principles, seven practices and seven processes. It sets out roles, stages and controls, and it can sit around predictive or agile delivery. If you are weighing it against the PMP, read PMP or PRINCE2 in Canada.

How to choose a methodology for your project

Ask four questions:

1. How stable are the requirements? Fixed and well understood points to waterfall; likely to change points to agile.

2. Can the work be delivered in pieces? If nothing is useful until everything is finished, a predictive approach usually fits. If each piece has value on its own, agile can deliver some of that value early.

3. How often can the customer review the work? Agile needs a customer or product owner who is available every cycle.

4. What do the contract and any regulator require? Fixed-price contracts, stage-gate funding and regulatory approvals pull towards predictive control, at least at the outer level.

If the answers point in different directions, you have a hybrid project. Choose deliberately, write down why, and revisit the choice if the project changes.

Which methodologies are on the PMP exam?

All of them, and none in particular. PMI's 2026 exam outline says about 40% of the questions use predictive approaches and the other 60% use agile or hybrid approaches. One of its first planning tasks asks you to assess the project's needs, complexity and magnitude, then recommend a development approach: predictive, adaptive/agile or hybrid.

So the exam does not ask you to recite a methodology. It describes a project and expects an answer that suits its approach: a backlog on an agile project, a change request through change control on a predictive one. Our guide to the five PMP exam topics explains how those questions work.

If agile is most of your work, the PMI-ACP may suit you better first; see PMI-ACP or PMP. If you want to prepare for the PMP with a trainer, see our PMP course: live weekend PMP training over 7 Saturdays, in person in Mississauga or online, from a PMI Authorized Training Partner (ATP #4456).