Project Management Methodologies: 8 Methods Compared, and How to Choose
By the end of this lesson you'll be able to:
- Explain waterfall, agile, scrum, kanban, lean, PRINCE2, the critical path method and hybrid in one sentence each
- Say when each method fits a project and when it does not
- Choose a best-fit method and a runner-up for a real project
Quick answer: what are project management methodologies?
Project management methodologies are structured ways of planning and running a project. The main ones are waterfall, agile, scrum, kanban, lean, PRINCE2, the critical path method and hybrid. In Kanbanchi's Project Management 101 course, you compare all eight and learn to pick one from how clear and stable your requirements are.
Eight methods in 8 slides
One idea per slide. Use the buttons, the dots or your arrow keys. The full text, with a comparison table, is right below the player.
Lesson 3 slides
8 slides
The full lesson: project management methodologies explained
What is a project management methodology?
A project management methodology is a structured way of planning and running a project: a set of principles, steps and roles that tells the team when to plan, how to deliver and how to handle change. It is different from the project life cycle you met in Lesson 1. The project life cycle is the series of five phases a project moves through: initiation, planning, execution, monitoring and controlling, and closing. The methodology decides how you move through those phases: once, in order, or in repeated short cycles.
There is no best method, only a best fit. The two questions that matter most are how clear the requirements are at the start and how often they will change. Clear and stable points toward predictive methods that plan up front; uncertain and changing points toward adaptive methods that plan in short cycles. Team size, regulation, delivery style and stakeholder involvement then narrow it down.
Here are the eight approaches beginners meet most often, each with when it fits and when it does not.
Waterfall
Waterfall is a sequential approach: the team finishes each stage (requirements, design, build, test, release) before starting the next, with scope agreed up front and one delivery at the end.
Each stage ends with a sign-off, and the next stage builds on it. The upside is predictability: you know the scope, cost and date early. The downside is that the customer sees a working result only at the end, so a wrong assumption made in requirements is found late.
Agile
Agile is an iterative approach: the team delivers working pieces in short cycles, gets feedback after each one and adjusts the plan as it goes. Its values come from the 2001 Agile Manifesto.
Agile is a family of methods and a set of values rather than one rulebook: scrum and kanban are the best-known ways to practice it. In agile projects, planning, execution, and monitoring and controlling repeat in every short cycle, while initiation and closing still happen once.
Scrum
Scrum is an agile framework in which a small team works in fixed-length sprints of one month or less, often two weeks, with three accountabilities: product owner, scrum master and developers.
Each sprint starts with sprint planning and ends with a sprint review and a retrospective, with a short daily scrum in between. The product owner orders the backlog, the scrum master helps the team work well, and the developers build the increment. Changes usually wait for the next sprint planning instead of breaking into the current sprint.
Kanban
Kanban is a flow method: the team shows all work on a board, limits how much work is in progress at once and pulls new work only when there is capacity, without fixed-length iterations.
Cards move across columns such as To do, In progress and Done. A work-in-progress limit, for example no more than two cards in progress, stops the team from starting everything and finishing nothing. Kanban is often described as a method rather than a full methodology, because it can sit on top of how a team already works. See Gantt vs Kanban for when a board is enough and when you need a timeline.
Lean
Lean is an approach that grew out of the Toyota Production System: it focuses on delivering what the customer values and removing waste, such as waiting, rework and unnecessary work.
Lean asks what the customer actually values, then removes the steps that do not add to it. Many agile and kanban practices, such as limiting work in progress, come from lean thinking.
PRINCE2
PRINCE2 is a process-based method, first developed for UK government projects, that splits a project into management stages with defined roles and a business case that is checked at each stage before the project continues.
The name stands for PRojects IN Controlled Environments. A project board approves each stage, and if the business case no longer holds, the project can be stopped in a controlled way.
Critical path method
The critical path method (CPM) is a scheduling technique that finds the longest chain of dependent tasks; that chain sets the shortest possible project duration, and any delay on it delays the whole project.
Strictly, CPM is a scheduling technique rather than a full methodology, but it is often listed with them because so many plans are built around it. Tasks off the critical path have slack, also called float: they can slip a little without moving the end date. Lesson 6 covers how the critical path shows up on a Gantt chart.
Hybrid
A hybrid approach combines methods: it typically plans the fixed parts, such as budget, milestones or regulated work, up front in a waterfall style and builds the uncertain parts iteratively in an agile style.
A common pattern is a waterfall-style plan for the budget, contracts and milestones, with agile sprints inside the parts where the team is still discovering what to build. Lesson 4 plays out the difference between the two sides of a hybrid.
Project management methodologies: the comparison table
| Method | In one line | Fits when | Does not fit when |
|---|---|---|---|
| Waterfall | Sequential stages, one delivery | Clear, stable requirements; fixed scope | Requirements that will change |
| Agile | Short iterative cycles with feedback | Uncertain or changing requirements | Fixed scope that cannot ship in pieces |
| Scrum | Agile framework with fixed sprints and three accountabilities | Product teams of about 4 to 10 people | An unpredictable stream of small requests |
| Kanban | Flow on a board with work-in-progress limits | Continuous work: support, content, operations | One large scope with a hard date |
| Lean | Maximize customer value, remove waste | Improving a repeated process | Planning a one-off project on its own |
| PRINCE2 | Managed stages, defined roles, business case per stage | Large or governed projects | Small, fast-moving teams |
| Critical path method | Scheduling by the longest chain of dependent tasks | Many dependencies and a hard deadline | Work whose tasks are still unknown |
| Hybrid | Plan the fixed parts, iterate on the uncertain parts | Projects with both fixed and uncertain parts | Projects where one method already fits |
One method per project is not a rule. Many teams use a hybrid, and many plans combine a method with a technique: scrum with a critical path for the hardware delivery, or kanban for ongoing work next to a waterfall plan for a launch.
Case study: a fixed design vs a product that changed as it was built
Two famous projects from Kanbanchi's Great Projects series show why the same method cannot fit everything: a fixed design built to thousands of drawings, and a product that was still changing months before its launch. All facts come from the linked Kanbanchi pages.
Fixed design
Eiffel Tower, 1887 to 1889
Buildings · Paris, France
Eiffel's drawing office produced 1,700 general drawings and 3,629 detailed drawings for the 18,038 different parts. They were made at his works and joined with 2.5 million rivets by about 300 workers on site, so the crew was assembling rather than inventing.
The deadline could not move: the Exposition Universelle opened on May 6, 1889. The critical stage, raising the four legs to meet at the first level, was done by the end of March 1888, and the main structure was finished on Mar 31, 1889, more than five weeks before the fair opened. The cost rose from an estimated 6.5 million francs to about 7.8 million, roughly 20 percent more.
Method lesson: with the design fixed up front and a hard date, a predictive plan built around the critical path works. This is waterfall and CPM territory.
Source: Eiffel Tower: planned vs actual, Kanbanchi Great Projects.
Product that changed as it was built
The original iPhone, 2004 to 2007
Software and IT · Cupertino, United States
The concept itself moved: Steve Jobs steered the project away from an earlier tablet concept, which later returned as the iPad. Apple never published a budget or internal schedule, and according to the account summarized on the Kanbanchi page, a demo a few months before the January 2007 unveiling went badly enough for Jobs to tell staff they did not yet have a product.
Apple announced the June date anyway and then had under six months to turn the demonstration unit into a product it could build and sell in volume. Hardware, software and design each had one leader: Tony Fadell, Scott Forstall and Jony Ive. The phone went on sale in the United States on Jun 29, 2007.
Method lesson: when the product is still taking shape, you cannot write every requirement up front. Work like this needs short feedback loops and clear owners, the territory of agile methods. The Kanbanchi page does not say which method Apple used, so treat this as a contrast in the kind of work, not a claim about Apple's process.
Source: Original iPhone: planned vs actual, Kanbanchi Great Projects.
Exercise: which method fits your project?
Answer six questions about a project you know, or load one of the examples. The panel shows which methods are still in the running, and the result explains the best fit and a runner-up.
Worked example
A new office building: requirements very clear and rarely changing, several contractors, heavy approvals, one final delivery, the client involved mainly at the start and end. Result: Waterfall, runner-up PRINCE2. Load it with "A new office building" below to see the reasoning, or answer for your own project.
Which method fits your project?
Question 1 of 6
How clear are the requirements at the start?
- How clear are the requirements at the start?
- Very clear: we know exactly what to deliver: points toward Waterfall, PRINCE2, Critical path method
- Mostly clear, with a few open questions: points toward Hybrid, PRINCE2, Critical path method, Scrum
- Fuzzy: we will find out as we build: points toward Agile, Scrum, Kanban
- How often will the requirements change?
- Rarely: once agreed, they stay: points toward Waterfall, Critical path method, PRINCE2
- Sometimes, mainly in some parts: points toward Hybrid, Scrum
- All the time: new requests every week: points toward Kanban, Agile, Lean
- How big is the team?
- 1 to 3 people: points toward Kanban, Lean, Agile
- A team of about 4 to 10: points toward Scrum, Agile, Kanban
- Several teams, vendors or departments: points toward PRINCE2, Hybrid, Waterfall, Critical path method
- How much regulation or formal approval is involved?
- Heavy: approvals, audits and contracts: points toward PRINCE2, Waterfall, Hybrid
- Some sign-offs at key points: points toward Hybrid, Critical path method, Waterfall
- Light: the team decides: points toward Agile, Kanban, Scrum, Lean
- How will the work be delivered?
- One final delivery on a fixed date: points toward Critical path method, Waterfall
- A new version every few weeks: points toward Scrum, Agile
- A continuous stream of small items: points toward Kanban, Lean
- How involved will the client or stakeholders be?
- At the start and at the end, mainly for sign-off: points toward Waterfall, PRINCE2
- In regular reviews: points toward Scrum, Hybrid, Agile
- All the time: they want to see value early and often: points toward Agile, Lean, Kanban
Still in the running
- Waterfall, score 0
- Agile, score 0
- Scrum, score 0
- Kanban, score 0
- Lean, score 0
- PRINCE2, score 0
- Critical path method, score 0
- Hybrid, score 0
Knowledge check: Lesson 3
Five questions on this lesson. Get at least 4 right to complete Lesson 3 and move your course progress forward. Each answer comes with an explanation.
Key takeaways
- A methodology decides how you move through the five life cycle phases: once, in order, or in repeated short cycles.
- Waterfall, PRINCE2 and the critical path method suit clear, stable requirements; agile, scrum and kanban suit uncertain or changing work.
- Scrum works in fixed-length sprints; kanban works in a continuous flow with work-in-progress limits; lean removes waste from either.
- Hybrid plans the fixed parts up front and iterates on the uncertain parts, and it is often the honest answer for real projects.
Try it on a real board: two methods, one set of cards
You can try a predictive and an adaptive way of working on the same cards in Kanbanchi:
- Create a board with three lists: To do, In progress and Done, and agree how many cards may sit in In progress at once.
- Add your project's tasks as cards and pull them across as you work: that is kanban.
- Give the cards start and due dates, then open the Gantt chart view to see the same work as a sequential plan.
- Link dependent cards on the Gantt chart and look for the chain that sets your end date: that is your critical path.
- Keep the plan for the fixed parts and the board for the uncertain parts: a simple hybrid.
This step is optional. The course works without an account, and your progress does not depend on it.
Project management methodologies: FAQ
What are the main project management methodologies?
The ones beginners meet most often are waterfall, agile, scrum, kanban, lean, PRINCE2, the critical path method and hybrid approaches. Waterfall plans everything first, agile and its frameworks deliver in short cycles, lean removes waste, PRINCE2 adds controlled stages, CPM schedules around the longest chain of tasks, and hybrid mixes them.
What is the difference between agile and scrum?
Agile is an iterative approach and a set of values from the 2001 Agile Manifesto. Scrum is one specific agile framework, with fixed-length sprints of one month or less and three accountabilities: product owner, scrum master and developers. All scrum is agile, but not all agile is scrum.
Is kanban a project management methodology?
Kanban is usually called a method rather than a full methodology. It visualizes work on a board, limits work in progress and pulls new work when there is capacity, and it can sit on top of the way a team already works, which is why it suits ongoing work so well.
Can you combine project management methodologies?
Yes. A hybrid approach typically plans the fixed parts, such as budget, milestones or regulated work, up front in a waterfall style and builds the uncertain parts iteratively in an agile style. Many teams also pair a method with the critical path method for scheduling.